Hi Jeremias,
Jeremias Maerki wrote:
> IFParser is also still missing the parse code for the structure tree. I
> guess I would defer the call to startPageSequence in the IFParser, then
> parse the reduced FO tree using a ContentHandler delegate, set that on
> the user agent and then call startPage
Ah, I see. Essentially, you're stuck in the case where the IF is loaded
from XML in which case the user agent hasn't received the structure tree,
yet. So, to visualize this:
Direct Rendering:
- Reduced FO tree is built using XSLT and set on the user agent
- DocumentHandler.startPageSequence is cal
Jeremias Maerki wrote:
> Not just like that (if at all). The content items being produced inside
> the page-sequence have to be linked into the structure tree. There are
> links (MCIDs) back and forth between the structure tree and the content
> streams. You have to have the structure tree availabl
Not just like that (if at all). The content items being produced inside
the page-sequence have to be linked into the structure tree. There are
links (MCIDs) back and forth between the structure tree and the content
streams. You have to have the structure tree available while you create
the page con
To those PDF specialists around here: am I right that the structure tree
could as well be converted into PDF at the end of a page sequence, as at
the beginning?
In other words: could the piece of code dealing with the structure tree
be moved from PDFDocumentHandler.startPageSequence to
PDFDocument
