Locale-TextDomain-OO
view release on metacpan or search on metacpan
lib/Locale/TextDomain/OO.pm view on Meta::CPAN
Create the lexicon singleton during compilation time.
Maketext is implemented here for moving existing projects to Gettext.
BabelFish is implemented for multi-plural in one phrase.
But use BabelFish in that case only.
BabelFish is much harder to translate (similar to maketext)
by translation office or automatic translation.
For combinded plurals watch the Gettext multiplural example.
In that case you have to write that awful long formulas but it is possibel.
Never use keys instead of English language in code.
You can't read, execute (with placeholders) or test your code without translation.
=head2 Why a new module?
This module is similar
to L<Locale::TextDomain|Locale::TextDomain>
and L<Locale::Maketext|Locale::Maketext>.
lib/Locale/TextDomain/OO.pm view on Meta::CPAN
Locale::Maketext allows 2 plural forms (and zero) only.
This is changeable,
but the developer has to control the plural forms.
He is not an omniscient translator.
Gettext allows as much as needed plural forms at destination language.
=item *
Maketext has a plural formula as placeholder in strings to translate.
Gettext has fully readable strings with simple placeholders.
Then a very good automatic translation is possible and this module helps you.
(Some projects have keywords instead of English language in code.
This module helps you to write readable, uncrypic code.
Programmers optimisation is a very bad idea for translations.
Never split a sentence.)
=item *
( run in 0.508 second using v1.01-cache-2.11-cpan-3cd7ad12f66 )