Re: utf8 horror stories

John Williams <[email protected]>
Newsgroups gmane.comp.web.mason.devel
Message-ID <[email protected]>
On Fri, 17 Sep 2004, Autrijus Tang wrote:
> On Thu, Sep 16, 2004 at 03:13:08PM -0600, John Williams wrote:
> > I tried changing it to this:
> >
> >         use encoding 'utf8';
> >         ${ $self->{buffer} } .= $_ foreach grep { defined } @_;
> >
> > But all the doubly-encoded utf8 strings came back, indicating that it is
> > still doing the latin1->utf8 conversion on the strings which are "off".
> >
> > I'm using perl-5.8.3, encoding-1.48, mod_perl-1.99_12.  Do I need to
> > upgrade something?
>
> Hmm.  Try specifying "use encoding 'utf8'" before loading the rest of Mason
> Modules, perhaps?  Also consider using encoding::warnings first (without
> "use encoding 'utf8'") to find out where did the conversion really occur.

Thanks for the suggestions.  encoding::warnings looks like it will be very
helpful.

For technical reasons I cannot try it on our web site for a few days, but
I'll let you when I get some results using encoding::warnings.

~ John Williams




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.