> Have you tried looking what those bytes (0xA1 0xE3 0xA5 0xEF 0xA5) map to in
> any of those encodings you tried ? If you disable the XSL step so as to get
> the intermediate DOM file produced, what does that document look like? Is it
> correctly encoded or not?
without the xsl transformation, the xsp file produces the xml file,
correctly encoded in UTF.
And good thing that you mentioned trying to map the bytes...
First, the bytes are not corrupted or anything, they are correct EUC
bytes. However, this was a string within <xsp:expr></xsp:expr>, which I
fetched from a database.
I do something like this:
<xsp:logic>
...
my $foo = $sth->fetchrow_array;
</xsp:logic>
<xsp:expr> $foo </xsp:expr>
That $foo is what's causing me the problem. If $foo happens to contain
EUC characters, AxKit chokes.
If I swap it with an ascii string, everything is peachy, XSP processing
and XSLT processing both work.
--d
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
