peter at dragonstaff.co.uk
Wed Oct 12 13:52:13 GMT 2011
On 12 October 2011 14:20, Duncan Garland <Duncan.Garland at motortrak.com>wrot=
> >>> Now, the article has some valid points about how Maketext does it wro=
> (like not being able to handle a verbatim gettext PO), so let's fix
> ** **
> Maketext does handle PO files. I know it won=92t handle the plurals
> construct. Is there anything else it trips up on?****
> ** **
> *From:* Stephen Clouse [mailto:stephenclouse at gmail.com]
> On Thu, Oct 6, 2011 at 11:06 AM, Andr=E9 Walker <andre at andrewalker.net>
> I don't know if it helps, but I've been researching a little about
> localization recently, and I came across this article:
> In summary, it states Locale::Maketext shouldn't be used =97 we should be
> using Locale::TextDomain instead. I'm considering it for my current needs.
> Any thoughts?****
> The article is rather biased -- it points out the speck in Maketext's eye
> while ignoring gettext's planks.
Indeed. I used Locale::Maketext
to handle the translations for 25 different language sites no problem
The scenario the author describes about getting your translators to fill out
the .po file was realistic, although now it is more a case of email around a
spreadsheet and when it comes back cut and paste the phrases into a .po
file. It worked well, apart from when I found Myanmar (Burmese) wouldn't
copy and paste reliably into vi.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Catalyst