Bug 37157 - Port fox:destination to FOP Trunk
Summary: Port fox:destination to FOP Trunk
Status: CLOSED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: pdf (show other bugs)
Version: trunk
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: fop-dev
URL: http://xmlgraphics.apache.org/fop/ext...
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-19 09:57 UTC by Jeremias Maerki
Modified: 2012-04-01 06:49 UTC (History)
1 user (show)



Attachments
sorry, wrong bug (51.51 KB, application/octet-stream)
2005-12-12 03:29 UTC, Nils Meier
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremias Maerki 2005-10-19 09:57:00 UTC
fox:destination needs to be ported from the maintenance branch to the Trunk.

Glen suggested there might be an equivalent in the XSL 1.1 WD, so it might be
good  scanning the spec for such a feature.
Comment 1 Andreas L. Delmelle 2005-10-19 21:49:40 UTC
[Me on fop-users: ]
On our extensions page, there is a warning about possibly all FOs with an id property generating 
named-destinations 'in some future version'. I guess that would indeed make the most sense, together 
with a port of fox:destination to the trunk, but *as an extension* to deal with the PDF-renderer specific 
parameters (like zoom settings, open-in-new-window etc.)
----

Just some further clarifications on the above:
In essence, what is called an 'explicit destination' in PDF consists of a 'page' component and the page 
co-ordinates to jump to, optionally also zoom/magnification settings to use. The reference to the page 
and the co-ordinates can easily be derived from the area corresponding to a FO in the document. 
Maybe all that needs to be done here is change the PDFRenderers treatment of the existing 'internal 
destinations' (?) If the internal-destination in the document doesn't need to be reachable from a 
location external to the resulting PDF, PDF's explicit-destinations and link-annotations would suffice. 
That isn't always the case, hence iiuc the idea of changing the default behavior for *all* FOs with an id 
property, and that is where 'named destinations' step in: define a dictionary of all possible destinations 
in the document, so that they are per se always reachable from outside of the PDF.

fox:destination could be used to allow renderer-specific configuration of the named destination, like 
zoom settings for the PDF-viewer app (maybe even usable by the AWTRenderer as well?).
Comment 2 Nils Meier 2005-12-12 03:29:24 UTC
Created attachment 17196 [details]
sorry, wrong bug
Comment 3 Andreas L. Delmelle 2007-07-14 01:29:44 UTC
Can this be closed? As I remember, Jay implemented support for PDF destinations a while ago...
Comment 4 Jeremias Maerki 2007-07-18 02:58:43 UTC
Nope, the documentation has not been updated, yet. :-(
Comment 5 Jeremias Maerki 2008-03-02 08:01:49 UTC
fox:destination has again been documented and can be used.
http://xmlgraphics.apache.org/fop/trunk/extensions.html#named-destinations
Comment 6 Glenn Adams 2012-04-01 06:49:21 UTC
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed