XLIFF 2.0
- Laura White (Unlicensed)
- Kenny Teves
This document outlines the capabilities and limitations of Enterprise's XLIFF 2.0 filter configuration.
Important
At this time, the Enterprise XLIFF 2.0 filter configuration supports a subset of the current XLIFF 2.0 core specification. As we continue to develop this feature, additional features of the specification will become available.
Supported Attributes
As more of the industry moves to XLIFF 2.0, Enterprise is offering preliminary support for the translation of XLIFF 2.0 files. We support the following elements or attributes, with limitations noted below.
Elements
- source
- target
Attributes
- translate
- srcDir
- trgDir
- type
- canResegment
Any attributes on the unit element or children elements will be lost with the exception of the items listed above.
Important: At this time, we do not provide support for optional XLIFF 2.0 modules, including translation candidates, glossary, validation, change tracking, etc. If any customer-specific metadata is included, it will not be parsed or retained at this time.
Limitations
- The above attribute values cannot be modified and will retain the values of the original imported file. Order is not preserved.
- Any elements under unit except for segment, ignorable, source and target will be removed in the merged file. This includes notes which are parsed and stored in the database.
- Inline codes are parsed and will appear as such in the workbench, but on merge all wrapper code elements will be lost (ph, pc, sc, ec). Only the original content of the inline codes will be preserved. originalData elements will be removed during merge.
- Units with translate="no" will still be imported, but locked in the workbench.
Enhancements Beyond the XLIFF 2.0 Specification
We offer several enhancements beyond the XLIFF 2.0 specification, including the ability to segment by paragraph (rather than by sentence). For more information, click here.
