如何将国际化添加到我的 Perl 脚本中？
我正在考虑向用 Perl 编写的成熟 CGI 应用程序引入多语言支持。 我最初考虑使用 Perl 哈希（存储在磁盘上）作为翻译文件来滚动我自己的解决方案，但后来我遇到了一个 CPAN 模块，它似乎可以满足我的需求（i18n）。
有人有 Perl 国际化（特别是 i18n CPAN 模块）的经验吗？ i18n 模块是多语言支持的首选方法还是我应该重新考虑自定义解决方案？
谢谢
I'm looking at introducing multi-lingual support to a mature CGI application written in Perl. I had originally considered rolling my own solution using a Perl hash (stored on disk) for translation files but then I came across a CPAN module which appears to do just what I want (i18n).
Does anyone have any experience with internationalization (specifically the i18n CPAN module) in Perl? Is the i18n module the preferred method for multi-lingual support or should I reconsider a custom solution?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
有一篇关于软件本地化的 Perl Journal 文章。 它将使您清楚地了解添加多语言支持时可以期待什么。 它写得很漂亮而且很幽默。
具体来说，本文是由编写和维护
Locale::Maketext，所以我建议该模块只是基于作者所付出的痛苦，很明显，作者必须忍受才能使其正常工作。There is a Perl Journal article on software localisation. It will provide you with a good idea of what you can expect when adding multi-lingual support. It's beautifully written and humourous.
Specifically, the article is written by the folks who wrote and maintain
Locale::Maketext, so I would recommend that module simply based upon the amount of pain it is clear the authors have had to endure to make it work correctly.如果您有时间，请查看一下 Jifty 框架 - 虽然最初很混乱，但它非常优雅且可用。
它们重载
_，以便您可以在代码中的任何位置使用_("text to translate")。 然后正常使用 Locale::Maketext 翻译这些字符串。它的真正强大之处在于，他们使用 Scalar::Defer 推迟翻译，直到需要字符串为止 这样您就可以随时开始添加字符串，甚至在您知道它们将被翻译成哪种语言之前。 例如在配置文件等中。这确实使 I18N 易于使用。
If you have the time then do take a look at the way the I18N is done in the Jifty framework - although initially quite confusing it is very elegant and usable.
They overload
_so that you can use_("text to translate")anywhere in the code. These strings are then translated using Locale::Maketext as normal.What makes it really powerful is that they defer the translation until the string is needed using Scalar::Defer so that you can start adding the strings at any time, even before you know which language they will be translated into. For example in config files etc. This really make I18N easy to work with.