How best to handle differing client terminology when working with neural machine translation?

Good morning,

In the case of clients who require the translation of the same term in different ways, is there any best practice when using NMT?

For example, on one project, I have the French term "chiffre d'affaires" that should be translated as "turnover". In another project, it should be translated as "sales". In another project, it should be translated as "revenue".

These different translations are to comply with client preferences and to be consistent with existing translations.

1) When post-editing NMT, does the fact that I change the machine-translated term get fed back to the NMT engine to affect future translations?

2) If so, can I prevent this by unchecking "update" in the machine-translation memory settings?

3) If I leave "update" checked, does this mean that the post-edited term will be applied until I change it again by post-editing the term again?

Is there any best practice for this situation?

Thank you.

Neil

Parents Reply Children
  • 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.

    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.

    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