Neil Allen

This sort of thing is handled perfectly with the right package for SDL MT Cloud as we have these features available:

Dictionaries: these are not Language Cloud Dictionaries they are specific to NMT and they allow you to "force" the use of specific terminology when working for a client that needs it.  This is why the app on the appstore also has these options:

We also have a feature called "Branding" which is essentially a list of non-translatables.

These features are not available as part of the FL freemium or Translator package yet.  This may change in the future.  If you are in a position to look at the Enterprise packages then let me know and I can find the right person for you to talk to.

Having said all of this... if you are  Freelance translator and just want this capability... after all who wouldn't!... then you might find it useful to look at these plugins all of which offer some support for "forcing" the translation you want:

https://appstore.sdl.com/language/app/mt-enhanced-plugin-for-trados-studio/604/

https://appstore.sdl.com/language/app/deepl-translation-provider/847/ (managed on the web UI for deepL)

https://appstore.sdl.com/language/app/rys-google-cloud-translate-nmt/775/

Ok, thank you Paul, that looks like exactly what I want.

I have sent a request to info@sdltrados.com about purchasing a subscription package and am waiting for them to come back to me.

In the meantime, when using NMT, is it better to un-check the "update" checkbox in the memory dialogue as I cannot see what good any project-specific feedback would do for the NMT engine?

Just one other question: the three plugins you mention don't seem to use the SDL NMT engine. I don't want to have multiple subscriptions to MT engines, I would rather just have one and it seems to make sense to keep it all with SDL, not least due to privacy issues. So does that mean I have to purchase an enterprise package to use dictionaries with SDL NMT?

Neil Allen

Neil Allen said:

the three plugins you mention don't seem to use the SDL NMT engine.

Correct.  These all use different providers, but they do support the use of a dictionarywhch is why I shared them with you.

Neil Allen said:

I would rather just have one and it seems to make sense to keep it all with SDL, not least due to privacy issues. So does that mean I have to purchase an enterprise package to use dictionaries with SDL NMT?

I'm afraid so.  This may change in the future, but for the time being these features are only available through an Enterprise account.  It might still be worth asking for a quote for the language pair(s) you need.  Maybe something reasonable could be done... I'm not sure on the pricing.

Neil Allen

Neil Allen said:

the three plugins you mention don't seem to use the SDL NMT engine.

Correct.  These all use different providers, but they do support the use of a dictionarywhch is why I shared them with you.

Neil Allen said:

I would rather just have one and it seems to make sense to keep it all with SDL, not least due to privacy issues. So does that mean I have to purchase an enterprise package to use dictionaries with SDL NMT?

I'm afraid so.  This may change in the future, but for the time being these features are only available through an Enterprise account.  It might still be worth asking for a quote for the language pair(s) you need.  Maybe something reasonable could be done... I'm not sure on the pricing.