I see. Fixing that will take a little longer and I have higher priorities right now (like pushing for the release). At least you currently land on the right page when clicking a link. I'll see to it that this issue doesn't get forgotten.
If anyone wants to try to implement the missing functionality, here you have a few pointers: - See BasicLinkLayoutManager, LinkResolver and PDFRenderer.renderInlineParent(). - PDF Reference 1.4, Chapter 8.5.3 "Action Types", see Go-To Actions. Looks like this in the PDF: 45 0 obj << /Type /Action /S /GoTo /D [24 0 R /XYZ 0.0 841.889 null] >> endobj - The idReferences Map in PageViewport is already there but not filled. That's where the information about the location of a target could be stored. Since the Renderer determines the absolute coordinates of a mark on a page, it's the renderer which will supply the location information to the PageViewport. - This whole thing should probably be looked at in concert with the old fox:destination extension object which we need to bring back to FOP Trunk at some point. On 20.10.2005 14:38:49 Sven wrote: > Well, it almost works :) > Just on thing: As far as i remember, PDFs are able not only to link at a > given page, but within an anchor in a page. I have attached another > document (sorry, its a bit larger this time, but without enough text you > can not reproduce the bug), that shows what i mean. Clicking in the > summary on one of the subchapter will lead you to the beginning of the > page, that contains the the subchapter, not to the subchapter itself on > the page. > > Thanks for your quick reply > > Sven > > > I've done a change that should fix the bug for you. Would you please > > update your working copy and retry? Please let me know if it works. > > Thanks for preparing the example FO file in the first place! That helped > > a lot. > > > > This is the fix: > > http://svn.apache.org/viewcvs?rev=326133&view=rev > > > > On 18.10.2005 13:00:25 Jeremias Maerki wrote: > > > > > >> Looks like you hit a bug in FOP Trunk. I'll need to investigate this a > >> bit more closely. I will get back to you. > >> > >> For the fop-devs: The internal-destination is properly set on the area > >> tree but the PDFRenderer doesn't find the right pageReference in > >> renderInlineParent() and thus skips generating the PDFLink object. Maybe > >> there's a general problem with forward references there. > >> > >> On 18.10.2005 12:33:34 Sven wrote: > >> > >> > >>> Hi there, > >>> i read about FOP's problem, not being able to display leaders & co > >>> as links. In my case i have just simple text that is used as an > >>> internal hyperlink. FOP renders the page successfully without any > >>> warning about missing referenced IDs, so i have to assume everything > >>> works fine. But indeed none of the links is "clickable". > >>> I am using the latest trunk from repository (revision 325900). Am i > >>> missing something important? Thanks for help :) > >>> > >> > > > > <snip/> > > > > > > Jeremias Maerki > > > Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
