On Wed, 2009-02-11 at 11:21 +0100, Nicolas Pastorino wrote: > Hi Kore, > > On Feb 10, 2009, at 15:59 , Kore Nordmann wrote: > > > Hi, > > > > Find the PDF generation requirements document for the document > > component > > attached. > > > > This document offers a first discussion base for a requirements > > specification of PDF generation, which is on the roadmap for this > > release cycle. It does not involve reading PDF (which would mean > > converting PDF to Docbook). > > > Here are some inline inputs : > * Not knowing so much about the PostScript and Latex formats, i am > wondering how far from PDF these could be, and if it would be worth > taking them into account. I guess they shall not be part of the first > implementation iteration, but having an open-enough design might help > integrating them eventually, if need be.
I guess PostScript will be similar enough to be embedded just as another driver, but some further research would be required here. I think I will take a deeper look at PS in the design phase to ensure at least forward compatibility. LaTeX on the other hand does not contain explicit layouting information itself, but is just another document markup format. It should be quite easy to convert Docbook to LaTeX given the existing infrastructure. Reading LaTeX on the other hand would be really hard, since it is common to use custom packages, which are basically macros, which again are a turing complete programming language. That said a proper LaTeX reader would require to implement a "full" interpreter. Thanks for the comments & Kind regards, Kore -- Mit freundlichen Grüßen / Med vennlig hilsen Kore Nordmann (GPG: 0xDDC70BBB) eZ Components Developer eZ systems Headquarters tel +49 (0) 231-9742-7750 | fax +49 (0) 231-9742-7751 k...@ez.no | eZ systems | ez.no
signature.asc
Description: This is a digitally signed message part
-- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
