2019.2

These styles make use of the CSS Flexbox Layout Module. For more information about that,
see W3schools: CSS Flexbox.
Translating templates
OL Connect has a built-in feature to automatically generate output and previews from one
template in different languages, and to pluralize certain words in the output.
When OL Connect generates output or creates a preview for a template, it looks for a translation
file that matches the current "Locale" on page325. If there is one, OL Connect uses it to
localize any elements that are tagged for translation, and to pluralize words as indicated.
For this feature to work, a template needs to have:
l
Content that is tagged for translation (see: "Tagging elements for translation" on the
next page) and, optionally, pluralization (see "Pluralization" on page439).
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559 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440.)
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.
Page 434