Problem

Sometimes other CAT-Tools produce in their TM and thus in their TMX-exports tag structures like those:

• <1><2/></1>
• <1><2><3/></2></1>
• <1></1>

Or also like those:

•  <1/><2/>
•  <1/><2/><3/>
•  <1/><2/><3/><4/>

And in translate5 those structures may be represented only by a single tag. This leads to loss of matches in analysis, when migrating from another tool.

Solution

We need 2 more options on TMX import in the UI:

First option: "Merge nested tag pairs"

If option is activated (default off): When ever in TMX there are nested tag pairs, independet of their nesting depth, translate5 TMX import will merge them into 1 single tag.

Second option: "Merge neighbouring self-closing tags"

If option is activated (default off): When ever in TMX there are self-closing tags next to each other without any content between them, those tags are merged into one tag.

If both options are activated,

the second merging is executed after the first one. What means, that nested tag pairs with neighbouring self-closing tags are merged into on single self-closing tag.