note
clinton
<p>As far at the i18n goes, I'd recommend using [mod://Locale::Maketext::Extract], which I recommend not because I'm the maintainer, but because it is good! I became the maintainer BECAUSE it is good and I wanted to make it better.</p>
<p>i18n is complex, and [mod://Locale::Maketext] adds the flexibility to solve issues like (eg) multiple forms of plural, differing word orders etc, while [mod://Locale::Maketext::Lexicon] and its companion [mod://Locale::Maketext::Extract] (with <c>xgettext.pl</c>) makes it easy:</p>
<ol><li>for your translators, because everything gets dumped to a .PO file, which they can edit with (eg) [http://www.poedit.net/|poEdit], and</li>
<li>for your programmers, because it'll parse your Perl code, templates and YAML and pull out the latest versions of strings that need translating -> less maintenance</li>
</ol>
<p>To get an idea of how it all works, read (in order):</p>
<ul><li>[http://search.cpan.org/~ferreira/Locale-Maketext-1.13/lib/Locale/Maketext/TPJ13.pod|Complexities of translating your interface]</li>
<li>[http://search.cpan.org/~ferreira/Locale-Maketext-1.13/lib/Locale/Maketext.pod|How Locale::Maketext solves these complexities]</li>
<li>[http://search.cpan.org/~drtech/Locale-Maketext-Lexicon-0.77/lib/Locale/Maketext/Extract.pm|The formats that xgettext.pl can handle]</li>
<li>[http://search.cpan.org/~drtech/Locale-Maketext-Lexicon-0.77/lib/Locale/Maketext/Lexicon.pm|How to integrate Locale::Maketext::Lexicon into your app]</li>
</ul>
<p>Clint</p>
756116
756116