Problem

t5memory TM may contain tags with id/rid that are not mapped by t5 to a corresponding tag from source during reverse replacement. However tags amount and positions are same. This leads to a segment being 100% match contains wrong tags.

Solution

Add new functionality to t5memory tagHandler which should have a guessing mechanism to try to map extra tags to source. Algorythm is next:

• grab all tags in source that were not found in target
• get all additional tags from target and try to guess corresponding extra tags in source
• replace guessed tag

What to test:

Changes were made only for t5memory and only t5memory integration should be tested.
Need to check how tags from t5memory are mapped in t5.
There is a new config which influences if tags should be guessed in case normal mapping did not work properly runtimeOptions.LanguageResources.t5memory.guessUnrecognizedTagsFromTm