On Sunday 24 February 2002 02:16, Daisuke Maki wrote: > > Ah, that's a problem I've had before :) The absolutely totally latest > > AxKit CVS *might* fix that problem. If it doesn't, you might want to have > > a look at AxKit::XSP::CharConv: > > > > <xsp:expr> > > <char:charset-convert from='EUC'>$foo</char:charset-convert> > > </xsp:expr> > > > > That should take care of converting whatever your input is to UTF-8 (you > > can use it to convert to whatever, so long as your iconv supports it). > > I looked at the CVS, and I don't think this issue is addressed. And > quite frankly, I don't want to have to add more taglibs for every > "outside" variable that I need to use, so I have a proposition: > > Is it ok if we force the result of a <xsp:expr> to be converted to UTF, > no matter what? Attatched is the diff of this proposition. > > This may be too naive and brute force of a way to address this, but > maybe this can trigger brighter minds to come up with a better solution. > In the long run the real problem is that Perl itself is not really "UTF Aware", and many of the libraries that supposedly do "XML Processing" don't really understand character sets properly either. Its just going to be a long while before software catches up to this entire issue. Try perl 5.7.1, at least it is a LOT smarter about understanding different encodings than earlier versions.
Personally I think the entire approach to char sets and i18n is dumb, but I guess this is hardly the place to get into that! > > --d --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
