On Wed, 6 Dec 2006, Marius Feraru wrote:
> Just my $0.02: I choose the opposite, upgrade everything to UTF8 ;-)
>
> > utf8 handling in perl is still fraught with peril
> I second you on that, working with Unicode content is a mess, but
> anyway, rather than having to deal with a myriad of encodings, I always
> choose Unicode... working harder (obviously) on getting "data" upgraded
> to Unicode (Encode::Detect is a useful helper _usually_).
I tried the opposite, but "everything" included strings returned from
DBD::mysql, DBD::Oracle, LWP::UserAgent, CGI, Apache2::Request and
Apache2::Upload, Text::CSV, Text::vCard, and many other other modules.
I believe the DBD modules handle utf8 better now at least, but they didn't
back when we started to do utf8.
> For upgrading to Unicode there is a nifty solution for Mason components:
> using "preamble" parameter appropriately:
>
> preamble => qq{use encoding 'utf8';\n},
Yes, that is the advertised solution, which is supposed to just assume
everything is utf8. I tried it, but it didn't work. YMMV.
I eventually tracked my problem down to a bug in perl itself.
<http://rt.perl.org/rt3//Public/Bug/Display.html?id=36248>
~ John Williams
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
