I've been having great fun with PerlQt and am getting close unleashing a couple of small apps on an unsuspecting world :)
The one area that I'm still uncertain about is how to handle i18n issues (yes I know many would say I should have done that first, but the apps ARE small).
I'm sure I'm not alone in having a fair number of existing modules that do not depend on Qt but need i18n. I therefore seem to have two possibilities:
1) Use one i18n framework for non Qt modules and the Qt i18n framework for Qt modules. That will pose maintainance problems, and I really dont like this idea.
2) Use one i18n framework throughout - this will by definition not be the Qt framework. It looks like the PerlQt developers have already thought of this as there is the puic -tr func option.
Can anyone who has been through this process already give me some advice - I'm pretty sure option 2) is the way to go, but which i18n modules should I use? CPAN has quite a few listed!
Thanks,
Rich
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been having great fun with PerlQt and am getting close unleashing a couple of small apps on an unsuspecting world :)
The one area that I'm still uncertain about is how to handle i18n issues (yes I know many would say I should have done that first, but the apps ARE small).
I'm sure I'm not alone in having a fair number of existing modules that do not depend on Qt but need i18n. I therefore seem to have two possibilities:
1) Use one i18n framework for non Qt modules and the Qt i18n framework for Qt modules. That will pose maintainance problems, and I really dont like this idea.
2) Use one i18n framework throughout - this will by definition not be the Qt framework. It looks like the PerlQt developers have already thought of this as there is the puic -tr func option.
Can anyone who has been through this process already give me some advice - I'm pretty sure option 2) is the way to go, but which i18n modules should I use? CPAN has quite a few listed!
Thanks,
Rich
OK, I've looked at this a bit more and can answer myself - hopefully this may be of use to others :)
The GNU i18n docs drove me mad - they're very dry (not quite W3C dry, but getting close). Then I found:
http://www.autrijus.org/webl10n/
A breath of fresh air and targeted specifically at perl, which led to:
Locale::Maketext::Lexicon
This can use standard .po files, and has a perl equivalent of xgettext to automatically extract messages flagged to be localized.
Combine this with something like kbabel (sorry, I dont know the gnome equivalent!) and my i18n needs are sorted!
Cheers,
Rich