Before You Import:
Respecting SDLXLIFF Languages
Make sure that you exactly match the language codes of the SDLXLIFF file with the language codes of your Memsource Project. E.g., if your SDLXLIFF file has "en-US" as target language, you have to select "English-United States" also in Memsource as the project's target language (not just "English"). The same for source language. If you fail to do so, your translated SDLXLIFF file may fail to be correctly processed in Trados Studio.
Using the correct SDLXLIFF file
SDL Trados creates specific directory structure for the project: SDLXLIFF files, TMs, TBs ect. Be aware, that only SDLXLIFF file from target directory can be imported to and translated in Memsource! SDLXLIFF file from source directory does not contain the information needed for translation - when imported into Memsource, the file will not be segmented properly and exported translated file will be empty.
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.
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 SDLXLIFF 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 SDLXLIFF trans-units will get imported into Memsource and will not be segmented by Memsource. 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 SDLXLIFF states are supported.
By default (if no rules are added), all SDLXLIFF trans-units in the exported target file will look identical to the source except that the target will be translated. To change the SDLXLIFF states e.g. from new to translated in the exported target SDLXLIFF file, Memsource segment statuses can be mapped to SDLXLIFF states.
Custom Export Settings
Map to specific target SDLXLIFF attributes based on MemSource segment statuses:
- Confirmed and locked
- Confirmed and not locked
- Not confirmed and locked
If a source SDLXLIFF 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 SDLXLIFF trans-unit.
Important Notice on Translating SDLXLIFF Files in Memsource
While SDLXLIFF files can be imported into a Memsource project, we typically do not advise our customers to translate these formats in Memsource as their standard practice. The reason is that these formats are proprietary and can be best translated by SDL software that has been designed for it. There may always be minor or even major incompatibilities when translating Trados bilingual files in a non-Trados software.
Also, there are important benefits that a user has to give up when translating SDLXLIFF files in Memsource. When a user imports a file for translation (e.g. MS Word) into a Memsource project, Memsource automatically pseudo-translates the file in the background and checks if it can be correctly exported and opened in the MS Word application. If this test fails, the file is disabled for translation until the problem has been fixed. This is a great feature because in this way we can provide a guarantee to our users that files they import into Memsource can also be exported back and opened in their native application. We cannot provide this kind of guarantee with Trados files.