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.
|
- TXTRenderer Brian T. Wolf
- RE: TXTRenderer Matthew L. Avizinis
- RE: TXTRenderer Matthew L. Avizinis
- RE: TXTRenderer Art Welch
- Re: TXTRenderer Louis . Masters
- Brian T. Wolf