XLIFF 2 feature support

Wordbee supports the XLIFF 2 features described in the OASIS specification.

Click Settings, select XLIFF and view/edit a filter:

Features and characteristics

Find below a subset of the XLIFF 2 filter features. XLIFF 1 does support the same options.

Comments

Tick the first option below to extract XLIFF notes to Wordbee comments:

We read <note> tags on <file> and <unit> level. File-level notes are attached to documents in Wordbee and unit-level notes are attached to either the source text or the translation.

The second option permits to save back changed or new comments back to the translated XLIFF.

HTML content

Optionally choose to interpret texts as HTML content and apply an HTML filter:

When choosing this option the system no longer looks for XLIFF style markup but applies the selected HTML filter instead.

Context field

The Wordbee context field is populated with the translation unit ID (<unit id="heading1"..:>).

The context can be viewed in the translation editor. If activated in the word count profile, the system gives more weight to memory matches with identical context.

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">

You need to enable reading out size limits:

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.

Enable reading this information, see below. The second line is applicable to XLIFF 1 files only.

Example:

<unit id="a1" name="exclude" slr:sizeRestriction="60">
	<res:resourceData>
		<res:resourceItem id="r1" mimeType="text/xml" context="no">
			<res:source href="resources\en\registryconfig.resources-en.xml" />
			<res:target href="resources\de\registryconfig.resources-fr.xml" />
		</res:resourceItem>
	</res:resourceData>

Preserve white spaces yes/no

Full support of xml:space attribute. The default whitespace mode can be set in the filter options:

Status

Optional mapping of the XLIFF "state" of a segment to the Wordbee translation status.

If the value is "approved" or "final" then the translation status will be set to green / OK. Example:

<segment state="final">
	<source><sc id="1" type="fmt" subType="xlf:b"/>First sentence. </source>
</segment>

Finally you can choose to save the Wordbee translation status back to the XLIFF file:

Non translatable segments

The filter lets you exclude segments from translation by various criteria.

Options are:

- Exclude units by their "id" attribute.
- Exclude source segments by their "state" value. Type a state value or regex.
- Exclude units by their "name" attribute (the restype option is available with XLIFF 1 only)
- Exclude units by a content in a note. For example, typing "exclude" in the pattern will skip any units that have a <note> containing this word.

CDATA

We fully support CDATA content such as in:

<segment>
	<source>Hello! <![CDATA[I am<br />Joe Schmoelz]]></source>
</segment>

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