The XLIFF 2.0 file filter by default imports files with the following extensions:
- files with the file header <xliff version="2.0">
Basic Import rules
- Import <note>
If selected, data from the <note> element will be displayed in the Context window, so that Linguists can view it next to each segment. Only a <note> in a <unit> is supported (according to XLIFF 2.0 standards).
- Save Confirmed Segments to TM on import
By selecting this option, all segments that get imported to Memsource as Confirmed will be saved to the project's translation memory in the Write mode.
- Segment XLIFF
With this option, standard segmentation will be applied. If this option is not checked, one element will be one segment. (Note that this can result in multiple sentences in one segment.)
- Interpreting linebreak/pagebreak tags
This option will cause XLIFF linebreak and pagebreak tags to create a new segment.
- Preserve whitespaces
- Copy source to empty target if segment is not imported
- Represent text with attribute "translate=no" as non-translatable tags
- Context key
The context in XLIFF 2.0 has to be in the unit element or unit descendants. The base node (context node) for the XPath evaluation is the unit element. The default XPath is: @id.
See our XPATH manual for more details.
Import Segment Rules
Adding rules to this section will change the default import settings. Rules can be combined or added using either the available form or added manually. Custom XLIFF states are supported. Separating arguments by a comma creates the AND logical relationship, while a new line creates the OR logical relationship.
By default (if no rules are added), all XLIFF trans-units will get imported into Memsource. Memsource will always segment <source> but not <seg-source> unless the user turns off segmentation completely. (In this case, nothing will get segmented). The status of all segments in Memsource after import will be not confirmed and not locked.
Custom Import Settings
- Do not import segment when
- Set segment confirmed when
- Set segment confirmed when
Export Attributes Mapping
Adding rules to this section will change the default import settings. Rules can be combined or added using either the available form or added manually. Custom XLIFF states are supported.
By default (if no rules are added), all XLIFF trans-units in the exported target file will look identical to the source except that the target will be translated. To change the XLIFF states (for example, from New to Translated in the exported target XLIFF file), Memsource segment statuses can be mapped to XLIFF states.
Custom Export Settings
You can map to specific target XLIFF attributes based on the following Memsource segment statuses:
- Confirmed and locked
- Confirmed and not locked
- Not confirmed and locked
Note: If a source XLIFF trans-unit is split into two or more segments in Memsource, all of these segments will have the attributes of the first segment once exported into target XLIFF trans-units.
Maximum Target Length
The maximum target length feature is supported only if:
- The file element contains slr:profiles with generalProfile="xliff:codepoints"
- and unit in the file contains the sizeRestriction attribute.
The maximum value is then set as the maximum length property of the segment.
Please note: When the unit is divided into more segments, all segments will have the same maximum length property. This will be equal to the maximum for the unit—in this case, the following warning is returned after import:
A unit is split to more segments, the maximum length limit will be checked for each segment separately.
Tag Content Visualized
The tag content of the source XLIFF file can be viewed in the Editor by going to Edit and clicking on Expand Tags. These tags can be edited via F2.