Wordbee supports the XLIFF 2.0 features as described in the OASIS specification.
...
| Info |
|---|
Document comments are not saved back to the file. Saving back is available for comments attached to segments only. |
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.). 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 aforementioned behaviour to take place, take into consideration the following prerequisites:
1) The XLIFF file that is going to be marked for online translation using this XLIFF configuration contains HTML content.
2) You have first configured the "Non-breaking tags" 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.
...
| Code Block |
|---|
<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:
...