translate5 supports the openTM2 native xliff in version 1.1 and 1.2.
translate5 imports source target content. Segmentation with MRK tags (<mrk mtype="seg">) are supported as well.
All kind of XLF tags (<g>,<x/>,<bpt>,<ept>,<bx/>,<ex/>,<it>,<ph>) are supported. If <sub> tags are contained in tags, they are imported as separate segments as well.
According to the XML specification and the XLIFF 1.2 specification the xml:space attribute is parsed and respected.
A default value can be set in translatet5 if whitespace should be preserved or not (config runtimeOptions.import.xlf.preserveWhitespace; boolean).
If the default value is true, all whitespace is preserved (since xml:space="default" should use the default value and not disable preserving at all).
If the default value is false, whitespace handling can be configured by the xml:space attribute as specified in the XLIFF 1.2 specification:
preserve. The value
defaultsignals that an application's default white-space processing modes are acceptable for this element; the value
preserveindicates the intent that applications preserve all the white space. This declared intent is considered to apply to all elements within the content of the element where it is specified, unless overridden with another instance of the
Word count (OpenTM2 Syntax only)
translate5 uses the word count information contained in openTM2 xliff to provide the word count of the project, if the word count is not submitted manually on import time.
Changes can be tagged in openTM2 xliff in the export using HTML syntax (be careful: this is not useful inside openTM2 and may break it. It is only for use on file level).