Context of the segment
When working with 101% matches from a TM, it is possible to choose what context will be saved with each segment. This context then can be used to determine if the match in TM is 101% (in-context match) with the translated text or only 100% (the source text is a match, but the context of the new text is different. This is important when the context of the segment results in two different translation of the same original text.
Example of context: female 'Project manager' is translated differently than male 'Project manager'. Both translations will be saved to the Translation memory and offered as 101% match only if the surrounding segments will also match.
3 Types of Context
- Generally, the previous and next segments are saved with the translated segment.
- However, in some file formats, the segment key is more important than context (YAML, JSON, etc.).
- In some other cases, you might choose to ignore the context completely and save the segments with no context.
The type of context which will be saved with the segment to your translation memory is set in the File Import Settings when the job is imported. Every file can be imported with different settings, which means that your translation memory can contain segments with different types of context.
File Import Settings
The Context and Optimization feature is set for each file imported as a new job in the File Import Settings. Please see our article on Creating a new job for more details.
- Automatic: The context type will be selected automatically based on the file type.
- Files imported with the context type "Segment Key": ANDROID_STRING, CHROME_JSON, DESKTOP_ENTRY, DTD, JAVA PROPERTIES, JOOMLA_INI, JSON*, MAC_STRINGS, MOZILLA_PROPERTIES, PHP, PLIST, PO (gettext), RESJSON, RESX, TS, XML_PROPERTIES, YAML*
- Other formats will be imported with the context type "Previous and next segment"
- Previous and next: Both the previous and next segment will be saved as context.
- Segment key: The segment key or the segment ID will be saved as context. This can be specified for the above mentioned "Segment key" file formats and also customized for:
- CSV, XML, Multilingual XML and Multilingual MS Excel files.
- No context: No context will be saved and translation will be always overwritten by the newest version.
* See Memsource Limits for the context limits in YAML and JSON files.
TM Matching Optimization
The translation memory match can be further optimized for the imported jobs in the File Import Settings.
- Previous OR next segment context as 101%
- If a match with the TM context has the same previous or next segment, it will be offered as a 101% match. Otherwise, it will require both the previous and next segment to match.
- Ignore tag metadata (enabled by default)
- If the tag's metadata in the job is different then tag metadata in the TM, the difference will be ignored, the tag metadata from the job's original segment will be automatically added to the job's translated segment.
- Penalize multiple 101% TM matches by 1%
- Generally, the newest 101% match is found and displayed, but with this option, when more then one 101% with a different target (translation) is found, then all 101% matches are displayed as 100% with an arrow signaling the penalization.
- In Pre-translate: when the Pre-translation threshold is set to 101%, segments with multiple matches will not be pre-translated.
- In Analysis: segments with multiple 101% matches will be counted as 100% matches.
Articles related to Translation Memory: