The moral of the story is that if your target language is not XML, then
you have to write your own tool to take it from XML to, let's say, HTML.
One way is to get into the XSL processor and add your own code, another
(less clean) way is to write something that post-processes the XML
representation of the target language.
Unless, of course, we change the standard.
[Paul Prescod]
>Well, we could require the output to be PDF or PostScript or something,
>but XML seems the most logical choice. The important thing is to recognize
>that we do have to choose *something*.
XSL seems perfectly well equipped to handle any text-based target
language. So why not let it?
I guess I don't see the same need to "choose something" or restrict it in
any way other than to say "you must produce text". There must be something
very important that we gain by insisting the target language be one thing
or another. Help me understand what this important thing is.
-- Andrew
Andrew Bunner
President, Founder Mass Quantities, Inc.
Professional Supplements for the Perfect Physique
http://www.massquantities.com