DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=37157>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37157 ------- Additional Comments From [EMAIL PROTECTED] 2005-10-19 21:49 ------- [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?). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
