W3C home > Mailing lists > Public > www-xsl-fo@w3.org > February 2004

Re: Render to HTML

From: Chris Cosentino <ccosenti@cisco.com>
Date: Fri, 20 Feb 2004 13:04:17 -0500
Message-Id: <4.3.2.7.2.20040220125634.02b616c8@cannon>
To: "Davis, Jeff" <jbdavis@firstam.com>
Cc: "'www-xsl-fo@w3.org'" <www-xsl-fo@w3.org>
The attachment that I received was named 
"VIRUS1_DETECTED_AND_REMOVED_92400001445_VIRINFO.TXT", and it was blank.

Was that the name of the file, or was it a virus?

HTML was never intended for paged printed output. The fact that your vendor 
uses it and gets acceptable output doesn't change the "square peg into a 
round hole" nature of the situation.

There is nothing in HTML that lets you define page limits.

FO is used to produce processing instructions to an application so that the 
application can produce PostScript or PDF output (some also do RTF and MIF).

On option may be to use Adobe Acrobat to open the HTML, somehow generate 
"pages" and save the output back to HTML, but I bet it is a long shot. 
Google can render PDF as HTML, but I have no idea if it prints well or not.

At Friday 12:50 PM 2/20/2004, Davis, Jeff wrote:
>Here is a little more background.
>
>We currently do XML -> XSLT -> HTML for the browser.   We have a vendor 
>that uses the final HTML to print with.  They are complaining the paging 
>doesn't work well as we all know.  One solution we have done in the past 
>that works is XML->Crystal Reports -> HTML which does a good job of doing 
>the paging.  The vendor would like to continue using HTML for printing 
>until they can convert their process over to printing PDF's.
>
>That's the reason for the question.
>
>
>The attached is an example of Crystal HTML output.  Don't be alarmed about 
>the data it is not real.
Received on Friday, 20 February 2004 13:07:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 October 2007 16:06:12 GMT