How do I stop Studio from querying Language cloud when the cell is already translated?

 In my settings I haven't selected 'Look up segments in MT even if a TM match has been found' but it does so anyways; so every time I open a segment to change a word or correct a typo, or even just to run the memory through the file, it queries the MT engine - I blew through 100,000 characters of the 400,000 allotted in under 3 hours.

Parents
  • Hi Arianne,

    It seems the answer I gave you, whilst a relevant workaround, is not correct in terms of how the option "Look up segments in MT even if a TM match has been found" actually works.  It is supposed to behave the way you wanted it to work, and it does under the right circumstances.

    The explanation I received this morning and have confirmed is as follows:

    Unknown said:

    If in the providers list, the MT provider is before the TM, the lookup will still take place, even if the option to “lookup only when no TM match is found is disabled”. This is because Studio searches through the providers in the order in which they are added. This order can be changed.

    So if in your providers list you have the Translation Memory first and LanguageCloud second, the lookup will take place only if that option is checked. If you have MT first and TM second, the lookup will take place anyway.

    So please try changing the order of the providers using these little arrows and then you should be able to work as you expected.  So change this:

    To this:

    Then all is well.  Thank you Mihai for the explanation and for picking me up on this!

    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
  • Hi Arianne,

    It seems the answer I gave you, whilst a relevant workaround, is not correct in terms of how the option "Look up segments in MT even if a TM match has been found" actually works.  It is supposed to behave the way you wanted it to work, and it does under the right circumstances.

    The explanation I received this morning and have confirmed is as follows:

    Unknown said:

    If in the providers list, the MT provider is before the TM, the lookup will still take place, even if the option to “lookup only when no TM match is found is disabled”. This is because Studio searches through the providers in the order in which they are added. This order can be changed.

    So if in your providers list you have the Translation Memory first and LanguageCloud second, the lookup will take place only if that option is checked. If you have MT first and TM second, the lookup will take place anyway.

    So please try changing the order of the providers using these little arrows and then you should be able to work as you expected.  So change this:

    To this:

    Then all is well.  Thank you Mihai for the explanation and for picking me up on this!

    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
No Data