-
Bug
-
Resolution: Fixed
-
None
-
High
-
In the communication with OpenTM2 the used tags are modified to improve found matches.
-
Emptyshow more show less
problem
Assume a TMX containing a lot of single tags in the form <it type="struct"/>.
If we try to find matches we never get 100% matches, we always got a penalty in the match rate.
For reproduction assume the following 5 Segments:
Segment 0: Anzahl Tests: <x id="1"/>
Segment 1: Anzahl Tests: <it pos="end"></mq:rxt displaytext="Tag2" val="@XXX_UPD$1"></it>
Segment 2: Anzahl Tests: <ph></mq:rxt displaytext="Tag2" val="@XXX_UPD$1"></ph>
Segment 3: Anzahl Tests: <it type="struct" />
Segment 4: Anzahl Tests: <it id=\"2\" \/>
If we request this TM with the segment "Anzahl Tests: <tag>" and the tag in different variants, we got different results.
| Tag Variants requested | Resulted Segments (id and matchrate) |
|---|---|
| <it pos="end"></mq:rxt displaytext="Tag2" val="@MNCS_UPD$1"></it> | 1: 100 3: 13 0: 13 |
| <g id="1"></g> <it type="struct"/> <x mid="1"/> |
0: 100 3: 100 4: 100 2: 13 1: 13 |
| <x id="1"/> โ This is the form we currently use | 0: 100 2: 13 1: 13 |
So with changing the single tags from <x id="1"/> to <x mid="1"/> is little effort but improves the found segments a lot.
Since this is a problem in OpenTM2 so far, a issue is created there too.
Since we can fix this on our side with little effort, we implement this fix.
- relates to
-
- Done
-
- Done
[TRANSLATE-2353] OpenTM2 strange matching of single tags
| Start Date [Gantt] | New: 23/Apr/24 5:00 AM |
| Status | Original: Final pull request made [ 10005 ] | New: Done [ 10000 ] |
| Workflow | Original: MittagQI Workflow [ 30393 ] | New: MittagQI Workflow with Peer [ 36479 ] |
| Link | New: This issue relates to T5TMS-34 [ T5TMS-34 ] |
| Link |
New:
This issue relates to |
| Description |
Original:
h1. problem Assume a TMX containing a lot of single tags in the form <it type="struct"/>. If we try to find matches we never get 100% matches, we always got a penalty in the match rate. h2. For reproduction assume the following 5 Segments: Segment 0: Anzahl Tests: <x id="1"/> Segment 1: Anzahl Tests: <it pos="end"></mq:rxt displaytext="Tag2" val="@XXX_UPD$1"></it> Segment 2: Anzahl Tests: <ph></mq:rxt displaytext="Tag2" val="@XXX_UPD$1"></ph> Segment 3: Anzahl Tests: <it type="struct" /> Segment 4: Anzahl Tests: <it id=\"2\" \/> If we request this TM with the segment "Anzahl Tests: <tag>" and the tag in different variants, we got different results. ||Tag Variants requested||Resulted Segments (id and matchrate)|| |<it pos="end"></mq:rxt displaytext="Tag2" val="@MNCS_UPD$1"></it>|1: 100 3: 13 0: 13| |<g id="1"></g> <it type="struct"/> <x mid="1"/>|0: 100 3: 100 4: 100 2: 13 1: 13| |<x id="1"/> โ This is the form we currently use|0: 100 2: 13 1: 13| So with changing the single tags from <x id="1"/> to <x mid="1"/> is little effort but improves the found segments a lot. Since this is a problem in OpenTM2 so far, a issue is created there too. Since we can fix this on our side with little effort, we implement this fix. |
New:
h1. problem Assume a TMX containing a lot of single tags in the form <it type="struct"/>. If we try to find matches we never get 100% matches, we always got a penalty in the match rate. h2. For reproduction assume the following 5 Segments: Segment 0: Anzahl Tests: <x id="1"/> Segment 1: Anzahl Tests: <it pos="end"></mq:rxt displaytext="Tag2" val="@XXX_UPD$1"></it> Segment 2: Anzahl Tests: <ph></mq:rxt displaytext="Tag2" val="@XXX_UPD$1"></ph> Segment 3: Anzahl Tests: <it type="struct" /> Segment 4: Anzahl Tests: <it id=\"2\" \/> If we request this TM with the segment "Anzahl Tests: <tag>" and the tag in different variants, we got different results. ||Tag Variants requested||Resulted Segments (id and matchrate)|| |<it pos="end"></mq:rxt displaytext="Tag2" val="@MNCS_UPD$1"></it>|1: 100 3: 13 0: 13| |<g id="1"></g> <it type="struct"/> <x mid="1"/>|0: 100 3: 100 4: 100 2: 13 1: 13| |<x id="1"/> โ This is the form we currently use|0: 100 2: 13 1: 13| So with changing the single tags from <x id="1"/> to <x mid="1"/> is little effort but improves the found segments a lot. Since this is a problem in OpenTM2 so far, a issue is created there too. Since we can fix this on our side with little effort, we implement this fix. See http://jira.opentm2.org/browse/OPENTM2-60 |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Test Ready [ 10005 ] |
| Status | Original: Selected for Development [ 10100 ] | New: In Progress [ 3 ] |
| ChangeLog Description | New: In the communication with OpenTM2 the used tags are modified to improve found matches. |
| Fix Version/s | New: translate5 - 5.0.15 [ 11506 ] |