Hi,
When FOP was updated to 0.95, the old fox:outline extension element (and its
descendant elements) for bookmarks was replaced with the XSL-FO 1.1 standard
fo:bookmark element and its children. The old fox:outline contained the
fox:destination elements, but they are not needed in the new bookmarks so they were
not retained.
However, if they are needed for olink destinations, then they should be restored. I'm
not sure where to do that, though. In the old fop.xsl, they were all contained in the
fox:outline structure, and were not placed on the destination fo:blocks. I guess the
id on the destination block was sufficient for connecting a reference through the
fox:destination element. Putting them all in the fox:outline was easy, as it could
all be done in one place.
Can fox:destination be put into the fo:bookmark structure without generating errors?
If not, can a fox:outline structure still be added along side the fo:bookmark
structure and not produce errors? Or does each fox:destination have to be placed on
the destination block itself? If the latter, then that requires making changes in
many places in the stylesheet for all the elements that might need them.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Mathieu Malaterre" <[email protected]>
To: "DocBook Apps" <[email protected]>
Sent: Monday, July 12, 2010 8:31 AM
Subject: [docbook-apps] PDF olinking and FOP
Hi,
I am wondering if anyone has a complete setup of docbook + pdf +
olinking working. After some research pdf olinking is documented as
not working with fop:
http://www.sagehill.net/docbookxsl/OlinkPrintOutput.html
I believe this is incorrect. I could get it working by patching
directly the output fo file to use the following syntax:
<fo:basic-link external-destination="url(my.pdf#dest=myid)">
to get the page syntax working:
<fo:basic-link external-destination="url(my.pdf#page=7)">
The corresponding my.fo should contains fox:destination named destinations (*):
<fox:destination internal-destination="myid"/>
I found out that the old fop.xsl was exporting fox:destination
elements, but not the new fop1.xsl...
Could someone please shed some light on the actual support of named
destinations in PDF using fop + docbook 1.75 ?
Thanks !
--
Mathieu
(*) http://xmlgraphics.apache.org/fop/0.95/extensions.html#named-destinations
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
