Hi!
As part of internationalisation for Opsview (http://opsview.org), I've
come across a limitation in the lookup of translated messages.
We've decided to use arbitrary keys as the message keys, rather than
the English text, but i-default (http://www.iana.org/assignments/lang-tags/i-default
) is not used by Maketext as the basis for all other languages, so we
get web pages that say "ui.messages.hostIsDown", rather than the
fallback English translation.
After a lot of debugging through, I've found this is a limitation of
Locale::Maketext::Simple, which Catalyst::Plugin::I18N uses.
The patch for Locale::Maketext::Simple is raised here: https://rt.cpan.org/Ticket/Display.html?id=47609
I've attached a patch to the tests in Catalyst::Plugin::I18N with a
tarball containing an i_default.po file which demonstrates the problem.
Is this a valid and/or useful?
Ton
As part of internationalisation for Opsview (http://opsview.org), I've
come across a limitation in the lookup of translated messages.
We've decided to use arbitrary keys as the message keys, rather than
the English text, but i-default (http://www.iana.org/assignments/lang-tags/i-default
) is not used by Maketext as the basis for all other languages, so we
get web pages that say "ui.messages.hostIsDown", rather than the
fallback English translation.
After a lot of debugging through, I've found this is a limitation of
Locale::Maketext::Simple, which Catalyst::Plugin::I18N uses.
The patch for Locale::Maketext::Simple is raised here: https://rt.cpan.org/Ticket/Display.html?id=47609
I've attached a patch to the tests in Catalyst::Plugin::I18N with a
tarball containing an i_default.po file which demonstrates the problem.
Is this a valid and/or useful?
Ton
Attached Files:
-
catalyst_plugin_i18n_test.patch (1.60 KB)
-
catalyst_plugin_i18n_test.tar (10.0 KB)