The XLIFF 2.0 file filter by default imports files with the following extensions:
with file header <xliff version="2.0">
Basic Import rules
- Import note
If selected, data from the <note> element will be displayed in Context window, so that linguists can view them next to each segment. Only <note> in <unit> is supported (according to XLIFF 2.0 standards)
- Saving Confirmed Segments to TM
By selecting the option Save confirmed segments to TM on import, all segments that get imported to Memsource as confirmed, will be saved to the project's translation memory in the write mode.
- Segment XLIFF
A standard segmentation will be applied. Otherwise one element will be one segment (can result into multiple sentences in one segement)
- Interpreting Linebreak Tags
The option interpret linebreak/pagebreak tags will cause XLIFF linebreak and pagebreak tags 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
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 unit element and 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, added using the available form or manually. Custom XLIFF states are supported. Separating arguments by 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 that 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 export settings.
Rules can be combined, added using the form or 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 e.g. from new to translated in the exported target XLIFF file, Memsource segment statuses can be mapped to XLIFF states.
Custom Export Settings
Map to specific target XLIFF attributes based on MemSource segment statuses:
- Confirmed and locked
- Confirmed and not locked
- Not confirmed and locked
If a source XLIFF trans-unit segments 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-unit.
Maximum Target Length
The maximum target length feature is supported only if:
- file element contains slr:profiles with generalProfile="xliff:codepoints"
- and unit in the file contains sizeRestriction attribute.
Than the max value is set as max length property of the segment.
Please note that when the unit is divided to more segments, then all segments have same max length property set to the maximum for the unit - in this case 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 visualized via Edit - Expand Tags and edited via F2 in Memsource Editor and Web Editor.