FO 1.1 WD: missing pieces (?)

Hi,

I'm maintaining code that transforms RFC2629-style ("xml2rfc") documents 
to FO (<http://greenbytes.de/tech/webdav/rfc2629xslt.zip>). This code 
historically used special cases to support various extensions in Apache 
FOP, AntennaHouse XSL Formatter and RenderX. Last week, I decided to 
standardize on XSL 1.1 WD features, and to use post-processing XSLTs to 
generate the extensions for the various backends.

This works just fine for bookmarks and index generation extensions (page 
ranges etc.).

Two things are left that aren't covered in the current working draft; 
maybe they should be considered.


1. Generating PDF destinations

Apache FOP has an extension for generating those 
(<http://xml.apache.org/fop/extensions.html#named-destinations>). The 
ability to produce them is of great importance if you want identical URI 
fragments to work for different media types with HTTP content 
negotiation (such as <http://example.com/rfc2518#rfc.section.1>, where 
the actual mime type (HTML, PDF...) is selected based on the client's 
accept header).

Note that this doesn't necessarily need to be any change to the language 
-- it would make perfect sense to generate a PDF destination for each 
"id" attribute in the FO document. However, right now none of the 
processors I'm aware of seems to do that.


2. Generating document information

RenderX supports adding document information to PDF output 
(<http://xep.xattic.com/xep/doc/spec.html#Document_Information>). This 
seems to be a both useful and trivial thing to do; it would be nice if 
there'd be a standard way to express this.


Note that both features seem to be specific to PDF output. Maybe a 
separate document for PDF output optimizations could cover this?


Best regards, Julian

Received on Thursday, 20 May 2004 06:30:00 UTC