Details
-
Bug
-
Resolution: Fixed
-
None
-
Medium
-
When dealing with segments where the tag order has changed between source and target, the order of tags was saved wrong and restored wrong from t5memory when re-using such a segment.
Description
problem
Assume a segment with flipped tag pairs between source and target in t5memory:
<?xml version="1.0" encoding="UTF-8" ?><tmx version="1.4"> <header creationtoolversion="0.5.61" gitCommit="4682688f * updated to 0_5_61 * fixed compilation issue" segtype="sentence" adminlang="en-us" srclang="en-GB" o-tmf="t5memory" creationtool="t5memory" datatype="plaintext" /> <body> <tu tuid="1" creationdate="20240219T143803Z"> <prop type="tmgr:segNum">0</prop> <prop type="t5:InternalKey">7:1</prop> <prop type="tmgr:markup">OTMXUXLF</prop> <prop type="tmgr:docname">TRANSLATE-3745</prop> <prop type="tmgr:author">PROJECT MANAGE</prop> <prop type="tmgr:context">9ee86dc022a3e222302fbdd1f73bd4e1_mrk-0</prop> <tuv xml:lang="en-GB"> <seg>The <bpt x="501" i="1"/><ph x="101"/><ept i="1"/> test is hot<bpt x="502" i="2"/><ph x="102"/><ept i="2"/></seg> </tuv> <tuv xml:lang="de-DE"> <seg>Heiß <bpt x="502" i="2"/><ph x="102"/><ept i="2"/>ist der Test<bpt x="501" i="1"/><ph x="101"/><ept i="1"/></seg> </tuv> </tu> </body> </tmx>
will lead to scrambled tags on pre-translation and in match panel.
Problem on translate5 side is, that the tag IDs sent to t5memory were started to be counted from the beginning of the content. So the request to t5memory was done with not or wrong matching tags between source and target
Problem on t5memory side: T5TMS-196