\&
\& Hello, \& Joe.
\& \&How are you today?
\& \& .Ve .PP You need to markup your template according to the \s-1ZPT I18N\s0 specification, which can be found at http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ZPTInternationalizationSupport .PP .Vb 11 \& \& \&
\& Hello, Joe.
\&How are you today?
\& \& .Ve .SS "Extracting I18N strings:" .IX Subsection "Extracting I18N strings:" Once your templates are marked up properly, you will need to use a tool to extract the I18N strings into .pot (po template) files. To my knowledge you can use i18ndude (standalone python executable), i18nextract.py (part of Zope 3), or I18NFool. .PP I use i18ndude to find strings which are not marked up properly with i18n:translate attributes and I18NFool for extracting strings and managing .po files. .PP Assuming you're using i18nfool: .PP .Vb 7 \& mkdir \-p /path/to/my/app/locale \& cd /path/to/my/app/locale \& i18nfool\-extract /path/to/my/template/example.html \& mkdir en \& mkdir fr \& mkdir es \& i18nfool\-update .Ve .PP Then you translate the .po files into their respective target languages. When that's done, you type: .PP .Vb 2 \& cd /path/to/my/app/locale \& i18nfool\-build .Ve .PP And it builds all the .mo files. .SS "Making your application use a Gettext translation service:" .IX Subsection "Making your application use a Gettext translation service:" Previously you might have had: .PP .Vb 3 \& use Petal; \& # lotsa code here \& my $template = Petal\->new (\*(Aqexample.html\*(Aq); .Ve .PP This needs to become: .PP .Vb 8 \& use Petal; \& use Petal::TranslationService::Gettext; \& # lotsa code here \& my $template = Petal\->new (\*(Aqexample.html\*(Aq); \& $template\->{translation_service} = Petal::TranslationService::Gettext\->new ( \& locale_dir => \*(Aq/path/to/my/app/locale\*(Aq, \& target_lang => gimme_language_code(), \& ); .Ve .PP Where \fBgimme_language_code()\fR returns a language code depending on \s-1LC_LANG,\s0 content-negotiation, config-file, or whatever mechanism you are using to decide which language is desired. .SS "And then?" .IX Subsection "And then?" And then that's it! Your application should be easily internationalizable. There are a few traps / gotchas thought, which are described below. .SH "BUGS, TRAPS, GOTCHAS and other niceties" .IX Header "BUGS, TRAPS, GOTCHAS and other niceties" .SS "Translation Phase" .IX Subsection "Translation Phase" The translation step takes place \s-1ONLY ONCE THE TEMPLATE HAS BEEN PROCESSED.\s0 .PP So if you have: .PP .Vb 3 \&Hello, \& Joe \&
.Ve .PP It most likely will not work because the tal:replace would remove the tag and also the i18n:name in the process. .PP This means that instead of receiving something such as: .PP .Vb 1 \& Hello, ${user_login} .Ve .PP The translation service would receive: .PP .Vb 1 \& Hello, Fred Flintstone .Ve .PP Or .PP .Vb 1 \& Hello, Joe SixPack .Ve .PP etc. .PP To fix this issue, use tal:content instead of tal:replace and leave the span and its i18n:name attribute. .SS "Character sets" .IX Subsection "Character sets" I haven't worried too much about them (yet) so if you run into trouble join the Petal mailing list and we'll try to fix any issues together. .SS "Limitations" .IX Subsection "Limitations" At the moment, Petal::I18N supports the following constructs: .ie n .IP "xmlns:i18n=""http://xml.zope.org/namespaces/i18n""" 4 .el .IP "xmlns:i18n=``http://xml.zope.org/namespaces/i18n''" 4 .IX Item "xmlns:i18n=http://xml.zope.org/namespaces/i18n" .PD 0 .IP "i18n:translate" 4 .IX Item "i18n:translate" .IP "i18n:domain" 4 .IX Item "i18n:domain" .IP "i18n:name" 4 .IX Item "i18n:name" .IP "i18n:attribute" 4 .IX Item "i18n:attribute" .PD .PP It does *NOT* (well, not yet) support i18n:source, i18n:target or i18n:data.