When working with 101% matches from a TM, the previous and following segments provide context that can be saved with each segment.
Context is used to determine if the match in TM is:
An in-context match.
Source text is a match, but context of the new text is different.
This becomes important when the context of the segment results in two different translations of the same original text.
In Czech, a female 'Project manager' is translated differently than a male 'Project manager'.
If surrounding segments create context that can be used to identify the difference, both translations are saved to the translation memory and are presented as a 101% match when the same context is provided.
The type of context which will be saved with the segment to the translation memory is set in job is imported. Every file can be imported with different settings.when the
A translation memory can contain segments with different types of context:
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 segments
Both the previous and next segment will be saved as context.
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.
In some file formats, the segment key is more important than context (.YAML, .JSON, etc.).
If context can be ignored no context will be saved and the translation will always be overwritten by the most recently modified version.
No context is also applied when the provided context is not found.