And what's the best method of generating PDFs from
these XML files?
One way is to use XSL:FO - I don't know if that's the best. One
problem if you are publishing to the web and to PDF is that you have
to maintain both an XSLT and an XSL:FO when a change is needed.
Another option maybe to publish to XHTML and then look for an XHTML ->
PDF conversion... I wonder if anyone has a solution for this now?
Prince is great for this:
http://www.princexml.com/
It's an XML to PDF engine that uses css to hold formatting information.
When your content is already XHTML and you have css that makes it ready
for screen display you can get a PDF that looks just like your browser
screen with no extra work (actually it's not perfectly identical, if
your pdf users are picky you need to treat Prince output as a browser
and test for that output just like you do for IE and Firefox).
If you want more features in your PDF, you can layer print only css on
top of your web stuff and get things like table of contents, print
headers and footers, page breaks (before sections for example), etc.
Because prince supports css3 you can do a lot of fancy stuff. Check out
boom for an example:
http://www.alistapart.com/articles/boom
Although prince is not an exact drop in replacement for FO, I still
think it could take over pdf generation for the vast majority of
documents that have a web representation.
----->Nathan
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--