This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: XSLT and Text Processing Languages
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: XSLT and Text Processing Languages
- From: "Pawson, David" <DPawson at rnib dot org dot uk>
- Date: Thu, 7 Sep 2000 11:21:56 +0100
- Reply-To: xsl-list at mulberrytech dot com
Paul Terray
> Conclusion :
> - For any other format -> XML, Omnimark is mandatory
> - For XML -> any other format, Omnimark is probably better
For (OM terminology) up transforms OM is really good,
'a poor mans perl'? (certainly easier to learn)
For XML -> any other format.... I'd caveat that with a rider,
Only if control type (non xml) output needed,
and probably better to determine on a wider basis, e.g.
what complexity of transform, what access to source data.
I find this argument weaker.
DaveP,
now having 0.02euro's worth:-)
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list