2020.1

HTML tags in translation entries
A translation entry may contain HTML tags, for example when part of the text is styled or when
there is a hyperlink in the text. HTML tags must not be translated or removed. Normally,
translators will recognize a simple bold or italic tag (<b>...</b> or <i> ... </i> respectively), but
more complex elements like hyperlinks could cause problems. The translator may accidentally
modify the tag, and break the hyperlink for example.
One way to avoid this is to split the text around and inside HTML tags into separate chunks, no
matter how short. Select the respective text in the template and select Wrap in Span from the
contextual menu. Subsequently tag the new <span> element for translation.
Alternatively you could also add a comment explaining that the HTML tag should not be
changed.
To add a comment, simply double-click the entry in the Translations pane and enter your
comment in the Comments field. Comments will be added to the POT file and are visible to
translators in their translation tools.
Pluralization
Ideally, in templates with variable data, the text automatically adjusts to numbers in the data.
Take for example the following line in a template:
"This order contains @num_products@ product."
In the output, the text "@num_products@" will be replaced with the value of a data field, a
number in this case. (See "Variable Data" on page337.)
The word "product" should only remain the same when the actual number of products is 1:
"This order contains 1 product".
In all other cases it should be changed into "products", e.g.:
"This order contains 10 products".
This topic explains how to make OL Connect dynamically select a singular or plural word,
depending on the value of a data field.
Adding plurals
Entering plurals, or text with plurals, is a natural part of the translation process of a template.
This process starts by creating translation entries as described in the following topic:
"Translating templates" on page434.
Page 439