A survery of gettext and I18N resources
I'm collecting notes on Perl modules, including articles, which impinge on this huge issue.
I'd be delighted if someone has beaten me to it, but if not, please comment freely...
o Perl modules:
- Text::Xslate
- I18N::Handle
- App::I18N
- Jifty::I18N
- Jifty::Script::Po
- encoding::source
- Encode::Encoder
- use Encode::Encoder qw(encoder);
- use Encode::Base64;
- my $encoded = encoder($unencoded)->base64;
- my $decoded = encoder($encoded)->utf8('base64');
- Warning: Return values are objects, so:
- $actual_string = qq<@{[encoder($unencoded)->base64]}>;
- Encode::Guess
- Text::GuessEncoding
- File::BOM
- Locale::MakeText
- Locale::TextDomain (wraps Locale::MakeText)
- Locale::Messages (sometimes broken)
- Locale::Maketext::Lexicon (sometimes broken)
- Unicode, especially for sorting:
- Unicode::Collate
- Unicode::Collate::Locale
o Articles:
- https://gist.github.com/ap/909197
- http://perladvent.org/2013/2013-12-09.html
- https://blogs.perl.org/users/aristotle/2011/04/stop-using-maketext.html
(Are things still this bad? I assume not)
which links to http://perlmonks.org/?node_id=898687
- http://www.perl.com/pub/2011/08/whats-wrong-with-sort-and-how-to-fix-it.html
Also:
While going thru the issues list of modules yesterday, I saw a ticket referring to the module (sorry, did not note it), which did not support Google's commercial V 2 API. Does anyone know which module that is? I'd like to have a category in this survey of such on-line resources.
I don't think Locale::TextDomain wraps Locale::Maketext. Anyway, that Perl 2013 advent calendar that you mentioned (http://perladvent.org/2013/2013-12-09.html ) convinced me last year to switch all my projects from L::Maketext to L::TextDomain. The Dist::Zilla plugin https://metacpan.org/pod/Dist::Zilla::Plugin::LocaleTextDomain also helps making things easy.
Well, what exactly might make you think Maketext’s design would have gotten better?
Admittedly, the change log is not impressive, but as an optimist I was just hoping things were, err, better....
Thanx for the correction. I did not check the code. I just copied that remark from a page I read yesterday.