#1101 No ID-bound matching in /tm/tmx2source

[msoutopico]

Preconditions

• Project with a XLIFF file (or another format that allows unit ID as the identifier for alternative translations)
• XLIFF filter tweaked to use <trans-unit> ID as the identifier for alternative translations</trans-unit>
• A repeated segment with same source text but different ID
• A TMX file at /tm/tmx2source with a ID-bound match for one of the repetitions only

OMT package attached nncluding those preconditions.

Steps to reproduce

Open the attached project, then:

1. Go to segment 2 or segment 4
2. Go to segment 3

Expected results

1. You can see Match for "Bar" as second source
2. You can see Match for segment #3 as second source

Actual results

1. As expected
2. No second source

Comments

If I rename folder /tm/tmx2source as /tm/auto or /tm/enforce and reload the project, then there's an ID-bound match and segment 3 is pre-translated.

[Thomas CORDONNIER]

Indeed, that was strange, the key was correctly loaded but not used for display. This patch solves the problem

[msoutopico]

Thank you so much for your quick reaction, Thomas. Your patch seems to fix the problem indeed!

[msoutopico]

Thomas, Is there anything I need to do to have the patch pushed to the code in the repository?

[Jean-Christophe Helary]

On Jun 8, 2022, at 2:21, msoutopico xinelo@users.sourceforge.net wrote:

Is there anything I need to do to have the patch pushed to the code in the repository?

Thomas has write access to the repository so just ask him.

[Thomas CORDONNIER]

Commit sent to Sourceforge (3855272e667ae85b0ffd35d0fca99ef0ffaaa528)

[msoutopico]

Thanks, Thomas.

[Hiroshi Miura]

released as 6.0