Dear Wiki user, You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" for change notification.
The following page has been changed by AndreasDelmelle: http://wiki.apache.org/xmlgraphics-fop/ExtensionsForPdf The comment on the change is: Updated sample + Changed naming to follow the PDF Reference more closely ------------------------------------------------------------------------------ {{{ <pdf:dictionary type="catalog" xmlns:pdf="http://xmlgraphics.apache/org/fop/extensions/pdf";> - <pdf:entry name="PageMode">UseNone</pdf:entry> + <pdf:entry key="PageMode" type="name">FullScreen</pdf:entry> - <pdf:entry name="PageLayout">SinglePage</pdf:entry> + <pdf:entry key="PageLayout" type="name">SinglePage</pdf:entry> - <pdf:dictionary type="normal" name="ViewerPreferences"> + <pdf:dictionary type="normal" key="ViewerPreferences"> - <pdf:entry name="HideToolbar">True</pdf:entry> + <pdf:entry key="HideToolbar" type="boolean">True</pdf:entry> - ... + <pdf:entry key="HideWindowUI" type="boolean">True</pdf:entry> + <pdf:entry key="NonFullScreenPageMode" type="name">UseThumbs</pdf:entry> + </pdf:dictionary> + </pdf:dictionary> }}} + The ''type'' attribute is the hint to make sure the catalog dictionary is treated special, and its entries are added to the PDF Document Catalog. The same extension can easily be used for other dictionaries, like ViewerPreferences. Using the same terminology as in the PDF Reference seems to make sense, as it's a PDF extension. Using the exact same possible values could lead to an easier translation to PDF. - The ''type'' attribute is the hint to make sure the catalog dictionary is treated special, but the same extension could be used for other dictionaries. - Using the same terminology as in the PDF Reference seems to make sense, as it's a PDF extension. Using the exact same possible values could lead to an easier translation to PDF. Thinking about it some more, and starting to prototype this idea, the ''entry'' object seems to be the key, as it is conceivable to also insert a dictionary by specifying it entirely as a PDF expression. Makes me wonder to what extent we should validate the contents... Ultimate flexibility vs. the risk of producing corrupt PDF in case of the slightest glitch/typo (?) For a prototype implementation, check out http://issues.apache.org/bugzilla/show_bug.cgi?id=45390 + Maybe the abstract pdf:entry object would better be replaced by strictly typed objects, i.e. pdf:name, pdf:boolean, pdf:number, pdf:array...? + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
