2019.1

l
Content that is tagged for translation (see: "Tagging elements for translation" on the
facing page) and, optionally, pluralization (see "Pluralization" on page855).
l
One or more translation files (.po). Each file gives translations in one language.
The files that hold the actual translations are not made in the Designer. They can be made in
any translation tool that accepts a .pot file as input, and outputs .po files.
l
The .pot file is exported from the "Translations pane" on page988 in the Designer. The
file contains a list of texts in the base language. In OL Connect this is the language in
which the template was originally written.
l
A .po file holds translated texts for one language. Each .po file has an entry by which OL
Connect recognizes the target language.
(See: "Exporting and importing translation files" on page857.)
These file types are widely used in translation software, so you can team up with a professional
translator or translation agency to translate your templates, or you can do it yourself using a free
online tool, such as the Poedit software.
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855.
Page 850