Problem

Currently the xliff_paired_tags is generating custom xliff tags and those kind of tags are send to the remote resources when requesting translation.

Ex:

opening tag will be: <t5x_1_1>

closing tag will be: </t5x_2_1>

single tag will be: <t5x_3 />

The problem is that some of the resources are not able to handle invalide xml and in some cases sentences which contains the above layout will contain invalide tags. Which leads to repairing requirement on our side.

This kind of structure was validate some months ago and back then was all fine and we did not run into any problems. But since 1 month, some of the services are just not handling this kind of layout.

Solution

Remove the extra id which represent the segment index from the tag so the paired tags are not different. 

 <t5x_1_1> should be  <t5x_1>

</t5x_2_1> should be </t5x_1>

 <t5x_3 /> stays as it is  <t5x_3 />