This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Strange Xalan behavior
- To: xsl-list at mulberrytech dot com
- Subject: Re: Strange Xalan behavior
- From: igort at multiconn dot com
- Date: Mon, 7 Aug 2000 16:54:01 +0200
- Reply-To: xsl-list at mulberrytech dot com
>Did you probably forget the semicolon ';' ?
>->
>  
>Perhaps the parser is looking for the end of the entity and therefore
>skips some end-tags .
Nope, I haven`t forgot to put semicolon, however, after some more digging,
I came up with the conclusion that this is problem with char-sets, once I
was able to run the XSLT with specified encoding that didn`t throw
"unsupported encoding exception" it worked fine,
still I am stucked with "unsupported encoding" problem now. I need to use
ISO-8859-8 encoding and Sun and IBM VM`s support this one, but MS VM (from
IE) does not ???!!! I`ve tried to add sun.io.ByteToChar* classes to
classpath and it didn`t help.
right now I am trying to figure out where exactly the Exception occurs, but
the code of Xalan/Xerces is quite complex !!!
perherps you could tell how can I extend encoding support for Xalan ???
Thank you in advance
Igor
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list