I took a look at the same link to an external PDF in separate FO files
generated from DocBook 4.5 and DocBook 5.0. In the <fo:basic-link> element,
here's what the external-destination attribute looks like in the FO file
generated using DocBook 5:
external-destination="url(filename.pdf#dest=id)"
Here's how the external-destination attribute looks in the FO file generated
using DocBook 4.5:
external-destination="filename.pdf#id"
The only difference in my toolchain is the XSLT processor. For DocBook 4.5, I'm
using Saxon 6.5.3. For DocBook 5, I'm using Saxon 6.5.5.
Regards,
Jeff
________________________________
From: Bob Stayton [mailto:[email protected]]
Sent: 2012-03-24 01:55
To: Jeff Powanda; [email protected]
Subject: Re: [docbook] Support for PDF fragment identifiers in DocBook 5
Hi Jeff,
There should be no difference between the ns and non-ns stylesheet versions.
That behavior is toggled by the stylesheet param 'insert.olink.pdf.frag', which
is set to zero by default in both stylesheet versions. Something else must
account for the change in behavior.
Can you check the .fo files for 4.5 and 5 to see if the #fragment identifiers
are present in the FO output?
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: Jeff Powanda <mailto:[email protected]>
To: [email protected]
Sent: Saturday, March 24, 2012 12:47 PM
Subject: [docbook] Support for PDF fragment identifiers in DocBook 5
When I upgraded from DocBook 4.5 to 5, I was pleased to discover that
PDF fragment identifiers now work as they should. When I click a link to
another PDF, it opens the referenced PDF and jumps to that location.
I was surprised at this because I'm using the same version of FOP (a
snapshot build of FOP 1.0) that I used with DocBook 4.5.
Do the DocBook 5 stylesheets handle fragment identifiers differently
than they did in DocBook 4.5? Just trying to understand why this works now.
Regards,
Jeff Powanda
Vocera Communications, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
