Paola

Can you turn off lookahead and try again?  Certainly the second problem seems to be related to this.  I can't comment on TUs not being saved at all yet, but please try disabling lookahead first and then see what happen.  It's under File->Options->Editor->Automation.

You say "There is no other TM than mine". So for me it seems, like would have the customer configured the TM settings in your project NOT in "Language Pairs -> All Language Pairs", but in "Language Pairs -> Specific Language Pair". When you add a TM to "Language Pairs -> All Language Pairs" while the project is configured to use "Language Pairs -> Specific Language Pair", this TM (or these TMs) will be simply ignored by Studio.

Here is the setting how it looks like:

In such situation you should:

• Either deactivate the TM settings under specific language pair OR
• Add your own TM under specific language pair

I always doubted the purpose of Lookahead, it has no advantages at all... I would simply remove this completely from future releases or at least make it DEACTIVATED by default. After a fresh Studio installation this is the first option I switch off...

Jerzy Czopik said:

I always doubted the purpose of Lookahead, it has no advantages at all... I would simply remove this completely from future releases or at least make it DEACTIVATED by default.

Hi Jerzy,

I think I'd agree with you on the default.  The usecase, at least the usecase with the least problems to look out for, is when you work only with MT and no terminology or TM at all.  In this case the advantage of not having to wait for a response is tremendous.  But until we have instantly adaptiveMT and people don't wish to use their other resources anymore the usecase for that is probably small to non-existent!

It can be quite useful, but we can see the number of problems people report that are based on not being able to retrieve results that have just been added, so it should certainly be an optional settings rather than the default... in my (and your) opion.

Done, and turning off Automation > Lookahead didn't change a thing.

These are my current settings:

OK, this might be I do not have such a wide perspective as you have. In my usecases, which seem to be very similar to many other people, there is ALWAYS a TM and mostly a TB (very often even several TMs and TBs) in the project configuration. And even in case I would have the best possible MT on earth, I would still keep at least one TM and some TBs in the project settings.

To make this option useful, it must be configured that way, that in similar cases as here, when the subsequent segments to translate are similar and the next following segment would directly profit from the translation entered in just confirmed segment, the system recognizes this and makes a refresh in the search despite the prefetched results. If lookahead would already have worked that way, there wouldn't have been any compliants about it.

Thank you. I have removed the TM from All Language Pair and let it only in the specific English > Italian pair (previously, it was listed in both screens). I have tried to update the Project TM, and I get this error:

However, I have checked my TM language pair and it matches English (UK) > Italian (Italy). What is wrong?

These are also the same language variant of my project/package (hovering with the mouse on the little flags in the bottom right corner, it reads English UK > Italian Italy)

Please make a screenshot of the settings for TM in ALL Language Pairs AND in English to Italian and then post here. Thank you.

Jerzy Czopik, here you are! Thanks for your interest and help! I really appreciate it!

Jerzy Czopik said:

And even in case I would have the best possible MT on earth, I would still keep at least one TM and some TBs in the project settings.

As I said... "But until we have instantly adaptiveMT and people don't wish to use their other resources anymore the usecase for that is probably small to non-existent!"

We're in complete agreement.