Sean,
At 10:47 AM 7/25/2003, you wrote:
In regards to the XHTML to PDF transformations and the responses received
from my original post:
...
My take-home message there
is that the methods are maturing to the point where the transformations
are now, at least, possible, but the HTML/XHTML variations mean that the
results of transforming to PDF are mixed at best. The cost/benefit ratio
isn't where it needs to be.
Yes, exactly. Also, people's requirements for the PDF are so various that a
generalized solution will also be difficult on that account.
A partial solution, however, would still be better than nothing. Really
what we may need is a kind of toolkit or box of templates. This merges into
the whole upconverting-from-HTML problem, which can be a bear. You may need
a whole production pipeline, starting with HTML Tidy, and possibly allowing
for some human editorial intervention (depending on what your HTML looks
like coming in).
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list