2019.1

Other ways to translate a template
The built-in translation feature is easy to use for labels and short texts in for instance invoices,
web forms, transaction email messages, and pack lists. It is less suitable for long texts like
insurance policies or terms and conditions.
l
For longer texts it is recommended to use a content management system in
combination with scripts.
l
It is also possible to use snippets or separate sections for translation purposes in
combination with scripts. For an example see: HowTo: Single-Script Translation and
Replace.
Translating a template
To make use of the built-in translation feature, take the following steps.
1. Tag content for translation. See "Tagging elements for translation" on the facing page.
2. Optional: enable the pluralization option on any translation entry that should conform with
the number in a certain data field; see "Pluralization" on page417.
3.
Export the entries on the Translations pane to a .pot file. See "Exporting a file for
translation (.pot)" on page419.
4. Open the .pot file in a translation tool (e.g. Poedit), translate the texts and/or enter the (text
with) plurals.
Or, if you work with a translator or translation agency, send them the .pot file.
The result is a .po file (one per language).
5. Import the .po file or files. See "Importing translations (.po)" on page419.
6. Set the template's Locale, or select the field that contains a Locale value, in order to get
output in the correct language. See "Changing the locale" on page309.
Translating snippets
"Snippets" on page266 get translated when they are inserted in the output, if the text is tagged
for translation (see "Tagging text in snippets" on page415).
Translating content that is inserted by a script
Personalization scripts may add content to the output. OLConnect will apply translations to that
content at the moment it is added to the template, for example with the html() or replaceWith()
Page 413