On Fri, 21 Jun 2002, [ISO-2022-JP] 大矢＠ＫＣＮ wrote:
> Thank you for your reply.
>
> >First, when an XPS file is being processed, you need to realize that
> >there are two distinct document fragments:
> >
> > a) the part which you are printing out via $t->{ XXXX }
> > b) the rest of the document, which is printed straight out of the
> >XML::XPath::* objects ( I think that's what it is, instead of
> >XML::LibXML objects, but it doesn't matter which in this context... )
>
> >So part b), which is the portion that you are not handling, is being
> >stored as UTF-8. However, I suspect that the charset you're using to set
> >the contents of $t in the XPS file is Shift_JIS. That's bad, because
> >that means you're mixing UTF-8 characters and Shift_JIS characters.
>
> Even if I save xml as UTF-8 file, nothing have changed.
> When I turn off AxOutputCharset shift_jis, page will display but Japanese characters
>from XPS doesn't recognize
> proper UTF-8.
>
> >For dynamically generated strings, you would need to convert them within
> >the perl code in the XPS file. Otherwise, you would need to convert the
> >entire document to UTF-8 format. You could use the iconv utility to do this.
>
> But with Axkit 1.4 or 1.5, I can mixup shift_jis(XML) and UTF-8(XPS) and output
>shift_jis.
> I hope install problem or something cause this...
I have a fear this might be the old "use bytes" issue with XPathScript.pm
again...
Try adding "use bytes;" to the top of XPathScript.pm and restart Apache
and see if the problem goes away.
--
<!-- Matt -->
<:->Get a smart net</:->
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
