How to make 99% matches 100%

[baktus]

I have aligned a project succesfully and am going through the Lingo project now. However, I have several files with segments with 99% match, but the 99% matched segment is actually matched 100%, but how do I change the match percentage so I can get rid of that light red color without changing the segment? Also, if I translate/confirm the segment shouldn't it be greyed anyway? It isn't even though I confirm the segment and save the file.

One really anyoing thing I have also found is a segment with several 100% matches. It seems that when I select one of the matches and save the file, the other match is shown the next time I open the file, but when exporting to Flare the first match is actually exported? Bug?

[Annemiek]

Hello,

I do not have the solution for the problem you mention, but I would like to add to the issue you mention about several 100% matches.
My French colleague is translating a project of ours (Dutch to French) and she has a similar issue. Mainly with 1 or 2 word segments. The TM a.o. contains segments with 1 word in small letters, including the accompanying translation in small letters, and segments with the same word starting with a capital letter inlcuding accompanying translation with a capital letter. Example:
Reservering - Réservation
reservering - réservation

Everytime she opens the index file (or any topic file fo that matter), the wrong segment is taken automatically if this 'wrong' segment happens to be on top of the suggestions.
Example in index file:

reservering (original) -

suggestions shown:
Reservering - Réservation
reservering - réservation

As the segment 'Réservation' is the first to be shown, it is taken automatically, although she previously (before opening the file) selected the correct segment with small letters (and saved this). This 'problem' keeps happening everytime she opens a file containing translated, 'confirmed' text segments. It is really starting to be a problem and we have no idea what to do about it... (The option 'Automatically apply translations to the rest of the file' at the Options is switched off)

Kind regards,
Annemiek

[baktus]

I have received an answer from MadCap support:

I have aligned a project succesfully and am going through the Lingo project now. However, I have several files with segments with 99% match, but the 99% matched segment is actually matched 100%, but how do I change the match percentage so I can get rid of that light red color without changing the segment? Also, if I translate/confirm the segment shouldn't it be greyed anyway? It isn't even though I confirm the segment and save the file.

"This is not currently possible in Lingo by design because the TM is conceived as a repository of translated strings only, but I certainly understand your desire for a quick visual confirmation that all content in a given file has been "touched" and decided on."

[techwriter31]

I'm experiencing the same problem and just submitted a bug about it.

What value does confirming and applying the correct translation have, if it is all dependent on where the segment falls in the list (when the list contains multiple 100% matches). At a minimum, confirming the translated segment (turning it grey) should move the segment to the top of the list to ensure it is always applied by default. Otherwise, no matter what translation changes are made, the same incorrect segment will be applied by default each time.

I thought I might be able to use the "Edit Translation Memory" option to delete the incorrect/unwanted segments, but everytime I select this option, Lingo stalls and crashes.

[techwriter31]

Update: MadCap tech support responded to this bug submission and confirmed that it IS a bug, and should be fixed in the next version of MadCap Lingo. The workaround for the time-being is to edit the translation memory and manually delete the translated segments.

I'm still having problems with Lingo crashing when I attempt to edit the translation memory. Tech support is helping me try to resolve this issue. I will post any relevant updates.