At 01:33 PM 5/15/2006, Nathan wrote:
You have tables created using ascii characters and you don't want your
document to look ugly? Good Luck!!!
I agree, that'll be a beast.
The "right" way to do it would be get those tables in XML, not in
plain-text pseudo-markup.
If the problem can't be fixed upstream, then XSLT 2.0 will be much
better than XSLT 1.0 for dealing with it. For example, if you're
lucky you might be able to tokenize your rows into cells (or infer
the proper widths of cells) using the string " | " as a delimiter.
That would be plenty lucky, however. At the opposite extreme (and
just as likely if not more so), if you have any cells spilling across
a single line -- that's really going to require wizardry.
Indeed, the nigh-unto-impossibility of such ad-hoc parsing chores is
a great deal of the reason behind standard syntaxes (like XML) for
markup languages to begin with.
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
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--