It depends. If you need to do text parsing, XSLT 1.0 will make it very
hard for you because of its very limited standard text parsing
functions. So, if you want to do what you said in your original post,
color highlighting of programming code, you will end up spending weeks
of coding in XSLT 1.0, where in XSLT 2.0 it would (possibly) be a matter
of hours.
So, "good idea" really depends. If you like to code and spend much time
to it, use XSLT 1.0, if not, and you rather use a tool that suits the
job better, choose XSLT 2.0 (or anything else that would make color
highlighting easier, there are many tools around that can do that readily).
-- Abel Braaksma
Mansour wrote:
I don't know if this would be a good idea at this point.
Michael Kay wrote:
Is there any way I can use replace with xalan.
The replace() function is new in XSLT 2.0, and Xalan only supports
XSLT 1.0.
Switch to Saxon.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
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>
--~--