Are there any way to control translation autoML

[yujf...@open-lc.co.jp]

Hi 

I am using google autoML to translate from English to Japanese in technical documentation.

I am using Sphinx to generate PO file and that convert to yaml file and

use autoML to translate msgid part and then put translated result to msgrd part.

Now, over the translation, "sudo" command comes in and translated by google AutoML as "須藤”, which is popular Japanese family name. Nothing to do with IT command.

Are three any way to control the translation. I mean not to translate

For some technical English, no need to translate and put that as is.

My understanding is glossary will not work in AutoML

and I entered the techincal jargon to data set but it looks does not work

Are there any way that I can control not to translate on some specific words?

I knew in html, you can add class=notranslate but I do not see the equivalent in text sentences.

Thanks

Yuji

[Music Li]

Hi Yuji,

You can use the Cloud Translation - Advanced API and it supports combining AutoML model and the glossary feature. 

Ref:

1. Glossary: https://cloud.google.com/translate/docs/advanced/glossary

2. API reference: https://cloud.google.com/translate/docs/reference/rpc/google.cloud.translation.v3#translatetextrequest

Best,

Music

[yujf...@open-lc.co.jp]

Hi Music,

Thank you very much and will test on it.

Many thanks

Yuji

2020年12月22日火曜日 2:25:50 UTC+9 Music Li:

[yujf...@open-lc.co.jp]

Hi Music,

Many thanks and I tested on my files and it worked!!

This removes my 18 months of headache that I can not control translation in google translation API v3.

Microsoft Windows translated to Microsoft "窓”, which is literally a ”Windows" in Japanese.

"Worker Process"  translated to "労働者” process, which in Japanese human labor process.

All are correct translations but do not make sense for IT documentation.

I used to review all 100+ pagers after Google translation completed.

 This really removes my nightmare.

One note, it may be obvious to everybody.

To make glossary work, you need to change

response.translations -> response.glosarry_translations.

I did not realize that first so I tested 5 times w/o changes and results are the same as before.

Now, I had a look at the use of the glossary section and found the change.

Again thank you very much

Yuji

2020年12月22日火曜日 20:42:11 UTC+9 yujf...@open-lc.co.jp:

[Music Li]

Hi Yuji,

Glad that it worked out for you, and thanks for letting us know :)

Best,

Music