Interface error with fuzzy match threshold

When I follow the steps to pretranslate a file and choose a different Minimum match value on the right pane of Batch Processing that is different from the Fuzzy match threshold, I get an error message: “The Pretranslate minimum match value cannot be set less than the Translation minimum match value.” This is an error, as the discrepancy lies in the Pre-translate Settings minimum match value, found in Options>Language Pairs>Batch Processing>Pre-translate files.

As an example, these are my current settings under Options:

When I was doing batch processing of 3 InDesign files, I normally went to Project>Batch Tasks>Pre-translate files. In the Batch Processing dialog box, I executed Task sequence: Pretranslate files, and clicked on Next. After selecting all the files I wished to pretranslate, I was faced with this dialog box:

Notice that my Minimum match value in the second screen is higher than the option I chose earlier. However, when I chose to lower it to 49%, I get an error message pointing to the wrong options to adjust:

The average user will go to the Options trying to find a Translation minimum match value and will not find it, because the correct option is “Minimum match value” in the Pre-translate Settings pane in the Batch Processing dialog box. 

Based on the mechanics of translation memory processing, this “minimum match value” is a fuzzy match threshold value because the TM engine calculates what is the fuzzy minimum value allowed to pretranslate segments.

Parents
  • Unknown said:
    Based on the mechanics of translation memory processing, this “minimum match value” is a fuzzy match threshold value because the TM engine calculates what is the fuzzy minimum value allowed to pretranslate segments.

    Hi Mario,

    I also don't think this is quite correct.  You can't call it a fuzzy because you may wish to set 100% and this would not be a fuzzy.  The term "Translation minimum match value" does seem to fit best I think.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply
  • Unknown said:
    Based on the mechanics of translation memory processing, this “minimum match value” is a fuzzy match threshold value because the TM engine calculates what is the fuzzy minimum value allowed to pretranslate segments.

    Hi Mario,

    I also don't think this is quite correct.  You can't call it a fuzzy because you may wish to set 100% and this would not be a fuzzy.  The term "Translation minimum match value" does seem to fit best I think.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children