>Perhaps what the OP means is that he had expected the [Fuzzy] feature to
>rely on the #3 match, which is what I think should happen. It is better
>to err on the side of caution, wouldn't you say?
I have this source segment: June 24, 2009 And I have configured OmegaT to insert 100% matches automatically. However, I have this segment in a TM: June 4, 2008...
... No, it is not. ... OmegaT used to do only 3 a long time ago, then we decided that it was not practical and made it do 2 (ie, ignore tags, numbers, ...
... Jean-Christophe Helary ... I think we should rather differentiate (both in terminology and technically) between a 100% match and an exact match. An exact...
... robertobech ... As you see yourself, it *is* a 100% match. What it isn't is a "repetition" (to use Trados terminology), i.e., the same exact segment....
... Expected by whom, though? The number "100" as a percentage seems to communicate to the user that something is "the same" or "exactly" as the other thing....
... I may have said it on that occasion, but Wordfast gives its users the option to report a 100% match as 99% if there is a difference in case, punctuation or...
... I would be for just having "100%" mean "extact". No matter the rationale to explain a "100% match", for the user it is just confusing to see a "100%" not...
I've been working with lots of files that have 100% matches on the TM, but I just can't trust OmegaT to this regard. The way it handles 100% matches, I'm...
... If you want OmegaT to handle exact matches as exact matches, merge your "safe" TMXs as project_save.tmx and open the project. Anything that is not...
Wouldn't it be safer to include a few lines of code to perform an exact-match test on the segment and TU if the initial match routine reports 100%, otherwise...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
Offline 
Send Email