Mike,
thanks for pointing this out as I simply ignored what goes on behind the
scenes.
I am using JDK 1.4.2 that comes with the installation of Oracle 10g Release
1.
I was checking out how to "replace" the default parser but I can't find much
in terms of documentation on this specific topic.
Is it just a matter of including a certain jar file into the classpath or is
there some configuration file that I need to alter?
I found a link apparently describing a similar operation but I can't find
any of the configuration files mentioned there, like java.args.
Thanks,
Flavio
----- Original Message -----
From: "Michael Kay" <mike(_at_)saxonica(_dot_)com>
To: "'Michael Kay'" <mike(_at_)saxonica(_dot_)com>;
<xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Thursday, December 08, 2005 09:38
Subject: RE: [xsl] Encoding problem or what else?
But you can use Saxon with a different XML parser.
More specifically, I think that it should work if:
(a) you use the default parser included with JDK 1.5, or
(b) you use JDK 1.4 and put the latest Xerces parser on your classpath,
invoking it in place of the Crimson parser that comes as the default
parser
in JDK 1.4.
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>
--~--
--~------------------------------------------------------------------
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>
--~--