Thank you for clarifying. Without the second explanation I really didn't see how that would help.
FYI: Our process creates customer invoices in fo and converts them to pcl using fop. This works fine and illustrates why we need fop. However, when a customer calls in to discuss their bill, the csr needs to be able to view the invoice on their screen. Our product runs on SCO Unix and is currently all text based. So the invoice the csr sees on their screen should be some sort of ASCII representation of what the customer has on paper in front of them.
We want to try to keep just one xsl so the different incarnations appear somewhat similar.
----- Original Message -----
Sent: Friday, October 12, 2001 11:05 AM
Subject: RE: TXTRenderer

What I meant was have you tried the following in place of using the fop text renderer option.  If text output is what you want, then you really wouldn't need fop at all; your XSLT engine would produce the output you want.
You didn't provide many other details,  so if assuming your using a stylesheet of some kind,
have you tried
<xsl:output method="text" indent="yes[or no]"/>
...the rest of the stylsheet...
You'd have more control over the output.
Hope this helps,
  Matthew L. Avizinis
Gleim Publications, Inc.
   4201 NW 95th Blvd.
 Gainesville, FL 32606
(352)-375-0772 ext. 101
-----Original Message-----
From: Brian T. Wolf [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 11, 2001 7:52 PM
Subject: TXTRenderer

Is anyone else using the TXTRenderer? It seems that when I try it my pages all appear twice as wide as they are supposed to and the letter spacing is all funky.
Is that already documented? If not, does anyone have any workarounds or ways to fix this?

Reply via email to