Page Comparison

Wordbee supports the XLIFF 2.0 features as described in the OASIS specification.

...

To view and edit the XLIFF filter options, go to Translation Settings > Document Formats and select XLIFF files. The XLIFF files - Configuration window opens. Here you can configure the following:

1. General settings
2. Do not translate settings
3. SDL XLIFF settings
4. QA settings
5. Web Preview settings

Image Removed

Image Added

Properties and settings

Find below a subset of the XLIFF 2.0 filter settings. Note: XLIFF 1.0 does support the same options.

...

Additionally, you can instruct the system to Split the text as HTML breaking tags. As a result, the system will NOT sub-segment the text at HTML breaking tags (eg: <p>, <div>.......etc.). Only tick Select this option only if XLIFF already contains translations and the translated HTML does not match the source HTML well, e.g. when the source contains two <div> tags whereas the translation contains just one.

For the aforemenitioned behaviour aforementioned behaviour to take place, take into consideration the following prerequisites:

1) Please make sure that the The XLIFF file that is going to be marked for online translation using this XLIFF configuration contains HTML content.

2) Make sure that you You have first configured the "Non-breaking tags" first in the HTML configuration that is attached to the XLIFF configuration. To configure the non-breaking tags, click on View to access the HTML settings.

...

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

Web preview URLs

XLIFF files may contain <res:reference href="{url}"> nodes. These can be extracted to segment-level custom fields. The option is found in the "Web preview" tab of the configuration:

Image Added

URL references may appear inside the <file> node as well as inside a <unit> node. The latter is given preference when extracting a URL for a segment. For example, if a file-node contains a reference it is assigned to every single segment, unless a segment explicitly specifies a different reference in its unit-node.

Example:

<unit>
	<res:resourceData>
		<res:resourceItem id="item-unit1" mimeType="text/xml" context="no">
			<res:reference href="https://myreference.com/page" />
		</res:resourceItem>
	</res:resourceData>
	<segment>
		<source>Source text</source>
	</segment>

Preserve white spaces yes/no

...