View Single Post
Old 08-27-2011, 10:46 PM   #3
AhShoo5n
Junior Member
AhShoo5n began at the beginning.
 
Posts: 9
Karma: 10
Join Date: Aug 2011
Device: Kindle 3
Please ignore previous content of this comment. I was looking at the wrong test PDF.

What I now see is a user-visible, hypertext-enabled, PDF ToC, i.e. exactly what you correctly identified. But I still don't really understand what is going on.

Outstanding questions:

1. If the converter sees the embedded ToC as mere text, why does it put link anchors around the ToC items in the epub HTML?

2. If, as it seems, the converter recognises that the PDF ToC is hypertext. Why can't the converter identify the link targets in exactly the same way as a non-Adobe PDF reader would do? I assume that the PDF standard is pretty explicit about how link anchors are encoded (i.e. no need for complex heuristics)?

Last edited by AhShoo5n; 08-27-2011 at 11:19 PM.
AhShoo5n is offline   Reply With Quote