On Saturday 23 February 2002 19:48, Daisuke Maki wrote:
> perl version if 5.6.1, I'm just trying to go from  EUC-JP encoded XSP
> file, and process it with another EUC-JP encoded XSL file.

I think this is unrelated to the Perl version. Almost everything should be 
happening at the libxml version, with Perl only seeing UTF-8 (if anything).

> ====
>
> [Sat Feb 23 10:37:25 2002] [warn] [client 127.0.0.1] [AxKit] [LibXSLT]
> performing transformation
> output conversion failed due to conv error
> Bytes: 0xA1 0xE3 0xA5 0xEF
> xmlOutputBufferFlush: encoder error
> output conversion failed due to conv error
> Bytes: 0xE3 0xA5 0xEF 0xA5
> xmlOutputBufferFlush: encoder error
> [Sat Feb 23 10:37:25 2002] [warn] [client 127.0.0.1] [AxKit] execution
> of: Apache::AxKit::Language::LibXSLT::handler finished
> [Sat Feb 23 10:37:25 2002] [warn] [client 127.0.0.1] [AxKit] writing xml
> string to browser
>
> =====

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?

> BTW Christian Glahn contacted me, and I somehow don't think it's
> XML::LibXSLT per se... I wrote a simple test ( which I've since sent him
> ) that did the XSLT translation to and from EUC-JP, SJIS, ISO-2022-JP,
> and UTF-8, and everything worked without a hitch.

It would take only one typo/omission in XSP.pm to rot certain encodings. 
That's why I'm curious about whether the output from XSP.pm is 100% correct 
in your case.

-- 
_______________________________________________________________________
Robin Berjon <[EMAIL PROTECTED]> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
"Chance is irrelevant. We will succeed." 
-- 7o9


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to