[docbook-apps] RE: [docbook] ulink and alternate transformations

[Jeff Beal <jeff dot beal at ansys dot com>]

How are you assembling the various chapters and sections of your book
together?  If you are using XInclude or standard XML external entities to
assemble your chapters into a single book and then building that book in a
single transformation process, all of those pieces can be considered part of
a single 'document', and <xref/> or <link/> are the preferred link
mechanisms.  If you are building each chapter in it's own transformation
process, what you propose with <ulink/> will probably be an acceptable
approach.

In general, though, if the source files are both maintained in DocBook,
you're going to have a lot more flexibility with how you link if you use
something other than <ulink/>.  If you currently have several stand-alone
chapters, I would strongly recommend looking into XInclude or external
entities to combine those chapters into a single 'instance' of XML so they
are more tightly connected.

Jeff

-----Original Message-----
From: Jeffery Biss [mailto:jeff@marco-inc.com]
Sent: Tuesday, October 28, 2003 10:50 AM
To: Jeff Beal
Subject: Re: [docbook] ulink and alternate transformations


Jeff,

They are other transformed files that are pointed to by the ulink. The
source is intended to be transformed into at least web accessible HTML and
PDF formats. someFile.html and someFile.pdf are other sections or chapters
of the current book and may be in another directory on the web server or CD
ROM distribution.

My confusion is not linking points within a single document but with linking
to the correct resultant file.ext when the single source XML is transformed
to two or more file formats. The file name remains the same while the
extension of that file changes as a result of its format.

I suppose that the type attribute could be used to define which extension is
added by the style sheet at transformation. For example: <ulink
type="format" url="someFile.">some file</ulink>

where format could be used to signal to the style sheet that the url
reference is to have the appropriate extension added at transformation, in
this case either html or pdf. If type is not present then the url value is
to be rendered explicitly as written. Does this sound reasonable?

Jeff



To unsubscribe from this list, send a post to 
docbook-unsubscribe@lists.oasis-open.org, or visit 
    
http://www.oasis-open.org/mlmanage/.



To unsubscribe from this list, send a post to
docbook-unsubscribe@lists.oasis-open.org, or visit
http://www.oasis-open.org/mlmanage/.




  

To unsubscribe from this list, send a post to docbook-apps-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.