Re: When must the structure tree be output in the PDF file?

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

Re: ambiguity of grammar for font shorthand?

On 23/09/2009, at 8:18 PM, Vincent Hennebert wrote: Hi Tony, Tony Graham wrote: On Mon, Sep 21 2009 23:30:17 +0100, jonathan.levin...@intersystems.com wrote: ... If inherit is allowed to be a value then the grammar truly becomes ambiguous since each of these can have the value inherit and

When must the structure tree be output in the PDF file?

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

Re: ambiguity of grammar for font shorthand?

Hi Tony, Tony Graham wrote: > On Mon, Sep 21 2009 23:30:17 +0100, jonathan.levin...@intersystems.com wrote: > ... >> If inherit is allowed to be a value then the grammar truly becomes ambiguous >> since each of these can have the value inherit and we don?t know which ones >> are >> omitted and mu