as others have said,it depends a lot on how general your input tables
are.
If all rows just take a single line, and there are no spanning entries,
converting to a real xsl-fo table would be esay in xslt2 and not too
hard in xslt1. If there are multiline or spanning entries like
--------------------------------
| this is a long 2 col heading |
--------------------------------
| this is | this is short |
| a long | |
| entry | |
--------------------------------
Then probably you should give in and use courier or a different
monospace font that doesn't look quite so horrible cmtt is OK for this.
Or use some pre-process with perl or somesuch to massage the tables
before giving them to xslt.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--