Tag content of source file can be visualized in the Editor by clicking Expand Tags under the menu and edited by clicking F2.
Files with the file header
ICU messages are automatically converted to Memsource tags. Files with ICU messages cannot contain any inline elements.
Data from the
<note>element will be displayed in the Context window.
<unit>is supported (according to XLIFF 2.0 standards).
Segments imported as Confirmed are saved to the project translation memory in Write mode.
Standard segmentation is applied. If not selected, one element will be one segment. This may result in multiple sentences per segment. If selected but one element is still one segment, the reason can be that the attribute canResegment="no" is present in the file. To push the segmentation, change it to "yes".
If the target segment is empty, the text in the source element is segmented. This behavior cannot be changed by enabling/disabling the option or adjusting segmentation rules.
XLIFF linebreak and pagebreak tags create new segments.
Context must be in either trans unit in elements context-group or context with context-type attributes.
The context must 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.
Adding rules changes the default import settings. Rules can be combined or added and can be applied using the available form or 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. Xpath can also be used in rules.
By default , all XLIFF trans-units are imported. If segmentation is performed,
<source> is segmented and
<seg-source> is not. The status of all segments after import is not confirmed nor locked.
Custom Import Settings
Do not import segment when
Set segment confirmed when
Set segment locked when
Adding rules changes the default import settings. Rules can be combined or added and can be applied using the available form or manually. Custom XLIFF states are supported.
By default, all XLIFF trans-units in the exported target file will look identical to the source excepting that the target will be translated. To change the XLIFF states, segment statuses can be mapped to XLIFF states.
Custom Export Settings
Specific target attributes can be mapped based on the following Memsource segment statuses:
Confirmed and locked
Confirmed and not locked
Not confirmed and locked
Not confirmed and not locked
When a 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.
maxwidth can be used to specify maximum target length for translation in these conditions:
Maxwidth must be in a trans-unit element (not in a group).
Size must be specified in
There is only one segment in the trans-unit element.
A warning is displayed if there are more segments in the trans-unit element.
The maximum target length feature is supported only if:
The file element contains
Unit in the file contains the
The maximum value is then set as the maximum length property of the segment.
In case of doubt, Drupal/WordPress XLIFF may be a good choice for any other XLIFF files as well where the translatable strings are in CDATA and contain HTML tags.