David Elliot wrote:

Hi Glen,

Sure that makes sense, FOP looks to be conceived as an Apache strength
XSL-FO -> PDF formatting utility/library that implements W3C's XSL-FO
standard - the end result being a library which task specific
applications can then confidently leverage.  Although, currently FOP
supports a variety of input formats - notionally image/graphic data
(BMP, EPS, GIF, JPEG, PNG, SVG or TIFF) - for inclusion during a
render.  Did this list of supported data formats evolve via
contribution, or is it strictly specified by standard ?

Many thanks,
David


I think we're talking two different things. FOP's input is still an XML document in the XSL namespace, those types above are graphics incorporated via fo:external-graphic or fo:instream-foreign-object. You would apparently like a new extension element then, possibly under fo:instream-foreign-object, that will allow for incorporating a PDF document.

PDF is not a graphic though. It is an output type, a document--so I guess you would need to write a parser for FOP to be able to translate the PDF document into XSL-namespace events that can subsequently be rendered on FOP's standard output types--PDF, PS, AWT, RTF, etc. That is out of scope for FOP. But if someone wanted it to contribute it to FOP, I would defer that to the rest of the team (I haven't been coding for awhile), but it would need to be pretty robust and solid -- not just a partly working system that will fill up the Bugzilla list with errors from people trying to use FOP just to concatenate PDF documents, or to convert PDF documents into other output formats. (Then again, that's how open source works... ;-)

Also, AFAICT the W3C XSL Working Group does not allow for embedding XSL documents within other XSL documents (i.e, placing an fo:root within an fo:root). Whatever their philosophical concerns are about such embedding may also be relevant for embedding PDF documents here.

Glen



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to