[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Olinks to different formats within the same document
Hi,
Yes, it is possible to link to the PDF version of
one document and the HTML version of a different document. An example
might make it more clear. Let's say you have userguide, confignotes, and
reference documents.
For each document, generate a targets file for each
of these, in both output formats (although you may not need them
all):
targets.userguide.html.db
targets.userguide.pdf.db
targets.confignotes.html.db
targets.confignotes.pdf.db
targets.reference.html.db
targets.reference.pdf.db
This requires running the process to
collect.xref.targets twice for each book, using the HTML stylesheet and the FO
stylesheet for each.
Let's say you are producing the PDF version of the
userguide, and you want to olink to the PDF version of confignotes and an online
chunked HTML version of the reference. The olink database document for
processing this userguide (using the FO stylesheet) would look something like
this:
<?xml version="1.0"
encoding="utf-8"?>
<DOCTYPE targetset [
<!ENTITY config SYSTEM
"targets.confignotes.pdf.db">
<!ENTITY ref SYSTEM
"targets.reference.html.db">
]>
<targetset>
<document
targetdoc="confignotes" baseuri="ConfigNotes.pdf">
&config;
</document>
<document targetdoc="reference"
baseuri="http://mysite.com/books/Reference">
&ref;
</document>
</targetset>
It uses the baseuri attribute to form the first
part of each link. When resolving an olink from the userguide to
confignotes, it creates a link like "ConfigNotes.pdf#mytarget". When resolving
an olink from the userguide to reference, it creates a link like "http://mysite.com/books/Reference/thispage.html#sectionid".
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]