I need to build a website (friends reunited style) which should be
multilingual from the start.

I am interested in hearing about real world experiences of i18n and
mod_perl (I'm using mod_perl 2). There are some new modules that have
become available since the last time this was discussed on this list :
http://marc.theaimsgroup.com/?l=apache-modperl&m=96755439927060&w=2

As I understand it, there are three issues:
1) Translating phrases into various languages to be grammatically
correct (especially where it involves numbers and word order)
2) Different cultures requiring different content
3) Localisation of dates/currency/sort-order etc

We probably need to support the major European languages.

* For the first issue, I've looked briefly at:

Locale::PGetText : http://cpan.uwinnipeg.ca/dist/Locale-PGetText
Locale::MakeText : http://cpan.uwinnipeg.ca/dist/Locale-Maketext
and Locale::Maketext::Gettext :
http://cpan.uwinnipeg.ca/dist/Locale-Maketext-Gettext

and our own Philippe's Apache::Language
(http://cpan.uwinnipeg.ca/dist/Apache-Language)

Does anybody have any experience of using these? How heavy are they,
given that I'll be using them in mod_perl and process size matters. Is
all of the functionality really required for most real world uses, or
can you get by on a roll-your-own basis or with Apache::Language, which
doesn't attempt to do anything except return translated phrases?

* For the cultural differences - I thought briefly about using the
multiviews approach with Template Toolkit templates, so the same data
may be presented differently for different cultures. While this does
require maintaining separate templates, it should mean that I will only
have to maintain the differences - anything that is common is only
written once.

* For locales, I was thinking about using (eg) DateTime::Locale
(http://cpan.uwinnipeg.ca/dist/DateTime-Locale) and
Locale::Currency::Format(http://cpan.uwinnipeg.ca/dist/Locale-Currency-Format).
As far as sorting goes, I'll be using utf8 for all data, and this should
be sufficient, no?

Any advice/best-practices/pitfalls greatly appreciated.

thanks

Clint


________________________________________________________________________

Clinton Gormley [EMAIL PROTECTED]

www.TravelJury.com - For travellers, By travellers



Reply via email to