forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.Pietschmann" <j3322...@yahoo.de>
Subject Re: DTD questions
Date Thu, 06 Jun 2002 21:41:37 GMT
Steven Noels wrote:
> Hey, cool down ;-)
Sorry, I was a bit disappointed that skin details got *much*
more attention than the somewhat more fundamental (and hard
to "fix later") structure details.

 >> 2.
> Ditto - could you come up with a revised DTD fragment. Let the people
> choose between a number of different link elements, and only one with
> all possible attributes folded in.

The DTD is ok.
diff -u document2html.xsl.bak document2html.xsl
--- document2html.xsl.bak	Thu Jun  6 21:00:55 2002
+++ document2html.xsl	Thu Jun  6 21:01:48 2002
@@ -384,12 +384,8 @@
     <a href="{@href}"><xsl:apply-templates/></a>
   </xsl:template>

- <xsl:template match="connect">
-  <xsl:apply-templates/>
- </xsl:template>
-
   <xsl:template match="jump">
-   <a href="{@href}#{@anchor}"><xsl:apply-templates/></a>
+   <a href="{@href}" target="_top"><xsl:apply-templates/></a>
   </xsl:template>

Of course, you see, the @role and @title attribute are unused.
I like the (your?) idea to use @title for a tool tip and/or
an onMouseOver() script and perhaps as text in case the
link is empty.
Personally, I don't like the idea that the link tag describes
the mechanic involved when clicking on the link *in a HTML page*.
As I already noted, if several xdocs are formatted into a PDF
book, there is no such notion as "replace viewport". If a link
expresses this, there is trouble.
We could organize around scopes (document, project/subproject,
ASF, world), presentation organization (HTML and PDF files)
or UI mechanics (replace window, replace frame, fork).
The first is the most abstract, with the other you already have
to nail down presentational aspects weh writing the xdoc.
A suggestion
- link within the xdoc <link href="#id">
   transforms to <a href="#id"> in HTML and
    <fo:basic-link internal-destination="id"> in FO
- link to another xdoc of the same project/subproject scope
    <link href="otherdoc.xml"> and <link href="otherdoc.xml#id">
   Note the .xml (or whatever the original extension is)
   Transforms to <a href="otherdoc.html"> respective
     <a href="otherdoc.html#id"> in HTML and
   <fo:basic-link internal-destination="geneate-id(element[@id])">
   in FO (avoid id clashes)
- difficult, therefore skipped: link within ASF or broader project scope
- link arbitrary URL <jump href="arbitrary">
   transforms to <a href="arbitrary"> in HTML and
    <fo:basic-link external-destination="arbitrary"> in FO
- indirect links, through a map (perhaps, but not necessarily a topic map)
    <xref ref="id"> (possible extensions: name map explicitely)
   transforms to
    <a href="document(map)/key('id',@ref)"> in HTML
   more complex logic for FO for discriminating between internal and
   external links.

>>4.
> This will take some more time, I believe. I don't want to impose yet
> another metadocument to manage to our users, but you have a point and we
> should fix this.
There is no requirement that the users *have* to use the
map/repository/metadocument. They *may* use it, and links
may be transformed from direct to indirect links and
vice-versa.

> Seriously: do you have a release date for FOP in mind?
There is a maitenance release pending in the short term,
however, I plan to overhaul the docs within 6-8 weeks.

J.Pietschmann




Mime
View raw message