Wordbee supports the XLIFF 2 features described in the OASIS specification.
Filter options
Click Settings, select XLIFF and view/edit a filter:
Features and characteristics
The XLIFF filter options are very exhaustive and let you enable or disable features such as:
- Comments
- Extract notes <note> on file and unit level to comments in the translation editor.
- Save back changed or new comments into the translated XLIFF file
- HTML content
- Optionally choose to interprete texts as HTML content and apply an HTML filter.
- Optionally choose to interprete texts as HTML content and apply an HTML filter.
- Size restrictions
- This requires the slr:profiles node with attribute generalProfile="xliff:codepoints". The maximum size restriction is then read from a unit node, such as: <unit id="a1" slr:sizeRestriction="60">
- This requires the slr:profiles node with attribute generalProfile="xliff:codepoints". The maximum size restriction is then read from a unit node, such as: <unit id="a1" slr:sizeRestriction="60">
- Reference material
- Such as links to images for the translator) from the <res:resourceData> node on file or unit level. The individual resource items are scanned for hyperlinks to reference material and extracted into Wordbee comments.
- Such as links to images for the translator) from the <res:resourceData> node on file or unit level. The individual resource items are scanned for hyperlinks to reference material and extracted into Wordbee comments.
- Preserve white spaces yes/no
- Full support of xml:space attribute. The default whitespace mode can be set in the filter options.
- Full support of xml:space attribute. The default whitespace mode can be set in the filter options.
- Status
- Optional mapping of translation status of a segment (<segment state="...") to the Wordbee segment status.
- Optional mapping of translation status of a segment (<segment state="...") to the Wordbee segment status.
- Non translatable segments
- By regular expressions
- Individual words or terms (for the purpose of hamper protection or obfuscation)
- By status
- By segment resource name (name-attribute)
- By text contained in an attached note
- CDATA
- We fully support CDATA content. However, in compliance with the XLIFF 2 specifications, translations are outputted without CDATA.
Limitations
There are also a few limitations:
- We do not yet read the canSegment attribute in the standard.
- The SDL XLIFF options in the filter are disregarded with XLIFF 2