On Saturday 23 February 2002 22:02, Daisuke Maki wrote: > 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.
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). -- _______________________________________________________________________ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com ----------------------------------------------------------------------- Designing pages in HTML is like having sex in a bathtub. If you don't know anything about sex, it won't do you any good to know a lot about bathtubs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
