Menu

#755 Source with different case shows as 100% match

None
closed-works-for-me
nobody
None
5
2015-09-02
2015-07-31
No

I have a segment "Indications For Use:" in a normal TM (tm folder), and a new segment in the source file that says "Indications for Use:". They differ only by the "f/F" in "for".
But the match is shown as a 100% in the three values.

Discussion

  • Didier Briel

    Didier Briel - 2015-09-02

    This is "normal". This is how OmegaT behaves since at least 1.8 (I suspect 1.6 or even 1.4 would be the same). You would get the same result with "indications for use:" and "INDICATIONS FOR USE:". If you move the TM to /tm/auto, however, you will note the translation will not be used automatically. This is because it is not an exact match. In OmegaT, a 100% is not necessarily an exact match.

    So it cannot really be considered a bug (it's "as designed"). I close as such. If you have suggestions on how to handle this better, you can do it as an RFE.

    Didier

     
  • Didier Briel

    Didier Briel - 2015-09-02
    • status: open --> closed-works-for-me
    • Group: 2.6 --> None
     

Log in to post a comment.