Many thanks for your answer. It seems that we have the same issue with other PDF readers; so this is unlikely to be a bug in Acroread.
We are left with the two other possibilitie (might also be a combination of both...), that is either a bug in FOP 1 or in Docbook FO XSL. For the later, I guess we can have some clues when looking at the intermediate FO file with and without using the incriminated FOP extensions. Meanwhile, how difficult would it be (and can we do this ourselves ?) To backport FOP 0.9 to XXE 4.8+ and build an XXE FOP 0.9 addon ? Many thanks for your help, Philippe. PS: The fact that this does not work with XEP was indeed one of the reasons for which we decided to stay with FOP, despite a couple of limitations. ----- Message d'origine ----- De : Hussein Shafie [mailto:huss...@xmlmind.com] Envoyé : Tuesday, June 07, 2011 07:54 PM À : nobili, philippe Cc : 'xmleditor-support@xmlmind.com' <xmleditor-support@xmlmind.com> Objet : Re: [XXE] OLinking does not work since XXE 4.8.0 (FOP issue) On 06/07/2011 05:57 PM, Philippe Nobili wrote: > > It seems that we are facing a serious issue with OLinking in DocBook PDF > output since XXE 4.8.0. It took us quite a bit of time to locate the > problem, since our DocBook customization has not changed for years. > > Now, we have found it and it seems related to apache FOP: > > When we attempt to use OLinks since XXE 4.8.0, instead of generating > appropriate PDF links, FOP generate link to the current PDF document > using a wrong PDF link fragment. Clicking on the link attempt to open a > Web browser.... The problem disappears if we comment the following line > out (excerpt from our XXE docbook layer): > > <parameter name="fop1.extensions">1</parameter> > > Needless to say, we absolutely need these extensions to get the side > navigational table of contents in our PDF outputs... and we use OLinks > quite a lot. > > Did we miss something, No. > and if not, is there anything that could be done > to restore the correct FOP behavior in XXE 4.8 or later ? If it's really a bug in FOP v1[*], that is, a regression from FOP v0.9, then the only solutions are: [a] Report the bug to the FOP dev team and wait for the next release of FOP. [b] Fix the bug in FOP v1 and contribute the bug fix to the FOP dev team. [c] Backport FOP v0.9 to XXE v4.8+. --- [*] It could be a bug in the DocBook XSL stylesheets or in Acrobat Reader. FYI, we are using RenderX XEP here at XMLmind and my Acrobat Reader 9.4.1 on Linux cannot follow olinks (translated to PDF) despite the fact that these olinks look good (in the tooltips displayed by Acrobat Reader). -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
