If you get that error, it is likely that it was transcoded sucessfully into
Unicode for internal use. But, of course, the code point 0x0000 is not a
valid XML character anywhere in a document so you get this error. So,
either the encoding is wrong but not wrong enough to make the transcoding
actually fail, or the source file has some accidentally embedded null
character somewhere or something like that probably.
Basically an encoding of "ISO-8859-1" could be used to decode any random
file, because every 8 bit value is a legal Latin1 character and every
Latin1 character is convertable to Unicode. So you could have a pretty
trashed file and it will decode ok, its just that it won't mean much to
whatever is trying to used that decoded stuff.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
"Scott Boag/CAM/Lotus" <[EMAIL PROTECTED]> on 01/26/2000 01:20:50 PM
Please respond to [EMAIL PROTECTED]
To: Dominique Broeglin <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re: Redirect
> Yes, if you look in the ps at the end of the mail, you have it.
Sorry. There I go reading emails too quickly again...
> > <?xml version="1.0" encoding="ISO-8859-1"?>
> I'm a dummy about encondings
I'm a dummy about them also. Since you have "An invalid XML character
(Unicode: 0x0)", it looks like you are possibly inserting a character
larger than 255 ("ISO-8859-1" only handles <= 0xFF, I think... but I'm
still not sure that explains the 0x0 char). You might want to try an
entity character reference (CDATA does not do the trick, if that was the
purpose of the CDATA brackets).
Someone on the Xerces side of things may be able to help more than me on
this sort of thing.
-scott
Dominique
Broeglin To: Scott Boag/CAM/Lotus
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED] cc:
i.fr> Subject: Re: Redirect
Sent by:
[EMAIL PROTECTED]
son.org
01/26/00
04:03 PM
Scott Boag/CAM/Lotus wrote:
>
> It looks as if is failing in the basic parse. Is your encoding attribute
> in the xml decl set up correctly?
>
Yes, if you look in the ps at the end of the mail, you have it.
It
seems that xerces doesn't like it. I'm a dummy about encondings and
other such things so I can't help anymore. Maybe if you have some
pointers I could try to hunt the issue deeper in the code...
Dom
> -scott
>
>
> Dominique
> Broeglin To:
"xalan-dev@xml.apache.org" <xalan-dev@xml.apache.org>
> <[EMAIL PROTECTED] cc: (bcc: Scott
Boag/CAM/Lotus)
> i.fr> Subject: Redirect
> Sent by:
> [EMAIL PROTECTED]
> son.org
>
>
> 01/26/00
> 12:02 PM
> Please
> respond to
> xalan-dev
>
>
>
> Hello (again ;-)
>
> I'm trying to use the redirect feature in order to handle
> images.
> I'm creating an XML document in which I insert a CDATA section
> created
> from a String (byte[], "ISO8859_1") string. It gives me exactly what I
> want (as far as I can see). After that I apply this stylesheet :
>
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform"
> xmlns:lxslt="http://xml.apache.org/xslt"
>
> xmlns:redirect="org.apache.xalan.xslt.extensions.Redirect"
> extension-element-prefixes="redirect">
>
> <xsl:template match="/">
> <out>
> begin
> </out>
> <redirect:open file="test.jpg"/>
> <redirect:write file="test.jpg"><xsl:value-of
> select="img"/></redirect:write>
> <redirect:close file="test.jpg"/>
> </xsl:template>
>
> </xsl:stylesheet>
>
> which produces :
>
> [EMAIL PROTECTED] LDAP]$ java org.apache.xalan.xslt.Process -IN test.xml -XSL
> test.xsl
> ========= Parsing file:/home/dom/directory/test/LDAP/test.xsl ==========
> Parse of file:/home/dom/directory/test/LDAP/test.xsl took 514
> milliseconds
> ========= Parsing test.xml ==========
> file:/home/dom/directory/test/LDAP/test.xml; Line 2; Column 16
> XSL Error: Could not parse test.xml document!
> XSLT: An invalid XML character (Unicode: 0x0) was found in the CDATA
> section.
> Xalan: was not successful.
> XSLProcessor: done
>
> Can someone help me on this topic ?
>
> Thanks,
>
> Dom
>
> ps: the xml file looks like this :
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <img><![CDATA[ .... ]]></img>