Menu
▾
▴
#1366 Add support for Microsoft neural machine translation (NMT) in Machine Translation
Currently, under 'configure' for Google Translate v2 there is a feature "Premium Edition".
I request the same for Microsoft Translator as the Neural translations are vastly better than the Statistical translations being fetched now (as it was with GoogleTranslate).
I don't know coding, but it appears to be a 1-line fix.
Background:
1. Microsoft Translator has 2 translating engines: statistical machine translation (SMT) and Neural (NMT). You can see both in action at once at https://translator.microsoft.com/neural
2. Right now, translations fetched by OmegaT match the SMT version.
3. It appears be a minor modification: "add the parameter “category=generalnn” to tell our service to use the NN models instead of the SMT " https://stackoverflow.com/questions/48104993/how-to-enable-dnn-translation-through-microsoft-translator-api
4. More is explained here: https://blogs.msdn.microsoft.com/translation/2017/11/15/microsoft-translator-accelerates-use-of-neural-networks-across-its-offerings/
5. A quote: "Any API call can use NN, you just need to use the category “generalnn” as a parameter to your API call" (https://docs.microsoft.com/en-us/azure/cognitive-services/translator/translator-info-overview)
This is all the info I could find. I hope it is helpful for the developers. Thank you as always for your amazing work.
Thanks to your detailed information, I was able to add the option.
Implemented in SVN (/trunk, rev. 10375).
Didier
Downloaded and tested. Neural translation in Bing working perfectly. Thanks!!
(Just FYI, since loading 4.1.4_1 my CPU usage (from OmegaT) has been jumping to 99.9% every couple hours, freezing OmegaT.
I installed JRE to run 4.1.4_1, so the JRE installation might be the cause.
This is just additional info in case you changed anything else and you or others are experiencing freezes. As for the code upgrade for this ticket, it is fantasic!! Thanks again. )
It could be an issue of not enough memory allocated to OmegaT.
If it is not the case, and if that can be constantly reproduced, you can open a bug report. I don't see it here.
Didier
I see. If you are not seeing it there, it seems unlikely to be the changes then.
I will try your suggestion and see how it works on my other computer when I have a chance.
In any case, the better functionality is worth an occasional reset for me. Take care.
Closed in the released version 4.1.5 of OmegaT.
Didier