Low quality translation compared to google live translator

[fissben]

I noticed that current repo isn't accurate translate anymore. Looks like it happened few weeks ago.

For example, im trying to translate from "en" to "ru" this phrase:
My apologies about my messages, hope they weren't too inconvenient. Hope everything will get back to normal soon.

Here is what I got from google in browser
Приношу свои извинения по поводу моих сообщений, надеюсь, они не были слишком неудобными. Надеюсь, что скоро все вернется на круги своя.

While library translate it like this:
Мои извинения о моих сообщениях, надеюсь, они не были слишком неудобны. Надеюсь, что все скоро вернется к нормам.

Which have a way more direct translation.

Any thoughts ?

[Stichoza]

Well, that's strange. Google sometimes provides multiple translations. I'll debug and see how to get most relevant one.

[fissben]

They also changed a way, how to deal with their server, new url came:
https://translate.google.com/_/TranslateWebserverUi/data/batchexecute..

i got only one user-agent to get same result, like we have in this library
Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0; Trident/6.0; IEMobile/10.0; ARM; Touch; NOKIA; Lumia 520)

But even this one works through new endpoint.

[Blair2004]

Hi, that's also what i've noticed.

The Google Translate (website) know some common brand terms... like WordPress, Elemenetor, etc. But the Google used on the package doesn't know that and will try to convert it into a random similar term for example, I tried to translate the sentence: "How to create a mega menu with Elementor"... it will convert Elementor to "Emoror", "Emerer", "Elementaire", "Element"... Which doesn't means nothing on the destination language (french).

I tried the approach of adding terms that shouldn't be translated on a tag with class "notranslate", but the translation is even worse.

[Stichoza]

Looked through the response coming from the server while using current URL. It does come with multiple versions of translation, but none of them are as good as ones translated by Google Translate website. The new URL that @fissben mentioned.

I guess we'll have to reverse engineer the new algorithm (cookies, etc). I'll post more updates here.

[fissben]

Here is working example of current endpoint (curl)

curl --location --request POST 'https://translate.google.com/_/TranslateWebserverUi/data/batchexecute?rpcids=MkEWBc&hl=ru&soc-app=1&soc-platform=1&soc-device=1&_reqid=53165&rt=c' \
--header 'authority: translate.google.com' \
--header 'pragma: no-cache' \
--header 'cache-control: no-cache' \
--header 'sec-ch-ua: "Google Chrome";v="89", "Chromium";v="89", ";Not A Brand";v="99"' \
--header 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 11_1_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36' \
--header 'content-type: application/x-www-form-urlencoded;charset=UTF-8' \
--header 'origin: https://translate.google.com' \
--header 'referer: https://translate.google.com/' \
--header 'accept-language: en-US,en;q=0.9,ru-UA;q=0.8,ru;q=0.7,ja-JP;q=0.6,ja;q=0.5,zh-CN;q=0.4,zh-TW;q=0.3,zh;q=0.2,uk;q=0.1' \
--header 'Cookie: NID=213=jMxpp4AcB9CbhtqMEgj78zOxP-71uc_Q_ku6ov-Ffd9FJYrCtiF5xLiWOBZtmQnBnvOXFJMY9qOjEBIA1o5HjiJwWZNisKzNHRO2ekwlsIfQJLsVMdaCBV0X_tNl4QVHbu6sWYniCdkXjDtVMjwID7EAtwTD2WpnD4p_Pr6F48hb_ffQMYXaWYNQDxgmb30jgTi4u0vLfaE1KddtC7E' \
--data-raw 'f.req=%5B%5B%5B%22MkEWBc%22%2C%22%5B%5B%5C%22%D0%9F%D0%B5%D1%80%D1%88%D0%B8%D0%B9%20%D0%BD%D0%B0%D1%86%D1%96%D0%BE%D0%BD%D0%B0%D0%BB%D1%8C%D0%BD%D0%B8%D0%B9%20%D0%BE%D0%BD%D0%BB%D0%B0%D0%B9%D0%BD%20%D0%BF%D0%B5%D1%80%D0%B5%D0%BA%D0%BB%D0%B0%D0%B4%D0%B0%D1%87%5C%22%2C%5C%22uk%5C%22%2C%5C%22en%5C%22%2Ctrue%5D%2C%5Bnull%5D%5D%22%2Cnull%2C%22generic%22%5D%5D%5D&at=AD08yZn3jSHJ2pLXRNZ-gYpVGrLd%3A1618314364485&'

After short investigation I've found that last part of payload at=AD08yZn3jSHJ2pLXRNZ-gYpVGrLd%3A1618314364485& is most important. Param at is what we are looking for. Somehow it generating hash of payload and then checking it on the backend. How it helps in reverse-engineering

[ermeh]

Yes, quality of translation is rather low when comparing with google translate. Why is that?

[henno]

We noticed this sudden degradation of translation quality a couple of weeks ago as well. Just found this issue. Has anyone made any tests after 18th of Apr or there any new information about as to why the quality of the traslations changed suddenly?

[Blair2004]

curl --location --request POST 'https://translate.google.com/_/TranslateWebserverUi/data/batchexecute?rpcids=MkEWBc&hl=ru&soc-app=1&soc-platform=1&soc-device=1&_reqid=53165&rt=c' \
--header 'authority: translate.google.com' \
--header 'pragma: no-cache' \
--header 'cache-control: no-cache' \
--header 'sec-ch-ua: "Google Chrome";v="89", "Chromium";v="89", ";Not A Brand";v="99"' \
--header 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 11_1_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36' \
--header 'content-type: application/x-www-form-urlencoded;charset=UTF-8' \
--header 'origin: https://translate.google.com' \
--header 'referer: https://translate.google.com/' \
--header 'accept-language: en-US,en;q=0.9,ru-UA;q=0.8,ru;q=0.7,ja-JP;q=0.6,ja;q=0.5,zh-CN;q=0.4,zh-TW;q=0.3,zh;q=0.2,uk;q=0.1' \
--header 'Cookie: NID=213=jMxpp4AcB9CbhtqMEgj78zOxP-71uc_Q_ku6ov-Ffd9FJYrCtiF5xLiWOBZtmQnBnvOXFJMY9qOjEBIA1o5HjiJwWZNisKzNHRO2ekwlsIfQJLsVMdaCBV0X_tNl4QVHbu6sWYniCdkXjDtVMjwID7EAtwTD2WpnD4p_Pr6F48hb_ffQMYXaWYNQDxgmb30jgTi4u0vLfaE1KddtC7E' \
--data-raw 'f.req=%5B%5B%5B%22MkEWBc%22%2C%22%5B%5B%5C%22%D0%9F%D0%B5%D1%80%D1%88%D0%B8%D0%B9%20%D0%BD%D0%B0%D1%86%D1%96%D0%BE%D0%BD%D0%B0%D0%BB%D1%8C%D0%BD%D0%B8%D0%B9%20%D0%BE%D0%BD%D0%BB%D0%B0%D0%B9%D0%BD%20%D0%BF%D0%B5%D1%80%D0%B5%D0%BA%D0%BB%D0%B0%D0%B4%D0%B0%D1%87%5C%22%2C%5C%22uk%5C%22%2C%5C%22en%5C%22%2Ctrue%5D%2C%5Bnull%5D%5D%22%2Cnull%2C%22generic%22%5D%5D%5D&at=AD08yZn3jSHJ2pLXRNZ-gYpVGrLd%3A1618314364485&'

When I still test this curl now it returns an output... so probably the value of "at" doesn't expire?

[Blair2004]

The work now is to extract the translated string from what looks like an incomplete json returned by Google.

464
[["wrb.fr","MkEWBc","[[\"Pershyy natsionalʹnyy onlayn perekladach\",null,null,[[[0,[[[null,37]\n]\n,[true]\n]\n]\n]\n,37]\n]\n,[[[null,null,null,null,null,[[\"First National On-line Translator\",[\"First National On-line Translator\",\"The first national online translator\"]\n]\n]\n]\n]\n,\"en\",1,\"uk\",[\"Перший національний онлайн перекладач\",\"uk\",\"en\",true]\n]\n]\n",null,null,null,"generic"]
,["di",156]
,["af.httprm",155,"6538938918244503432",158]
]
26
[["e",4,null,null,536]
]

[Stichoza]

so probably the value of "at" doesn't expire?

It's possible that it doesn't expire, however the value of that parameter differs for each different string. It's some kind of hash but I cannot find out how to generate it

[Blair2004]

What abotu using this

curl 'https://www.google.com/async/translate?vet=12ahUKEwjT7Maf1O_wAhUDBGMBHdhEBykQqDgwAHoECAIQJg..i&ei=XZqyYJPKMIOIjLsP2ImdyAI&yv=3' \
  -H 'authority: www.google.com' \
  -H 'sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36' \
  -H 'content-type: application/x-www-form-urlencoded;charset=UTF-8' \
  -H 'accept: */*' \
  -H 'origin: https://www.google.com' \
  -H 'x-client-data: CIe2yQEIpLbJAQipncoBCOH2ygEIqJ3LAQigoMsBCKygywEI8fDLAQiB8ssBCNzyywEIqPPLARiOnssBGJH1ywE=' \
  -H 'sec-fetch-site: same-origin' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-dest: empty' \
  -H 'referer: https://www.google.com/' \
  -H 'accept-language: en-US,en;q=0.9,fr-FR;q=0.8,fr;q=0.7,sw-TZ;q=0.6,sw;q=0.5,es;q=0.4,de;q=0.3' \
  -H 'cookie: SEARCH_SAMESITE=CgQIyZIB; SID=-AdTEiYBHQxwyi6tM21CKmx0c4Y1a4q433Cacx-mQACfzwIH0I1fT0wH7pVmUnd_kK_QOA.; __Secure-3PSID=-AdTEiYBHQxwyi6tM21CKmx0c4Y1a4q433Cacx-mQACfzwIHKrDd2zvJ_c5gnPl4a2MMeA.; HSID=Ayll6tzipONjmj1m4; SSID=AqEGOJ5K3d9zhN9JB; APISID=iY7F7EQuWx9eYks1/AAK2jCg-YLchJ2xIx; SAPISID=2ZivtOqq29XgIoHy/ArdWxr5KbTd4RtM9J; __Secure-3PAPISID=2ZivtOqq29XgIoHy/ArdWxr5KbTd4RtM9J; OTZ=5999998_52_52__52_; NID=216=Ni17mzF6uLOBNG4iasK6JP9GjDmN9BbP-VFSNdu6KgFipkAdhdzCVYo9IWOCbkvmHa6HYd7VAaWO40EnGURxQYczydEHbQFatNbk5wDnZwBw0I8aJN8xlpNDynCxs5vHahDdOSFuEt2ppr-BK90W816xk3QOlzDgU1pyHWv0dJqMEVbpSNDIxUCZAJz8GO1oJq5fv1JfJQDYYZ1BJO6EUXww8kdlmGIrNzhmAAvKHUnhu7PKv98OY6EHT39EMC187f1ewAVZV7zlSgcAKNEzgxcFh6PhtMHH6srqOkxkm0E-6oK1l5KBZZSXkvDvDXu_bD-2t8hj0m8-R7hASU5u9AiScP7zjcxumRtpEt1vRA9WHeLCY-EZQ5R8T1A7vpigqpsh9x8O9zOqRkgXcq4R7zL-ww3ohf3chjkQwLX5J9xLnMreSKQ; 1P_JAR=2021-05-29-19; DV=w-LWwaovX_lHMO5HzDUyvBMlILCam9c7hOlmyewo2gAAACAcuD9TMkTrYAAAAGDtw7_cZzBvRwAAAA; UULE=a+cm9sZTogMQpwcm9kdWNlcjogMTIKdGltZXN0YW1wOiAxNjIyMzE3NjY0MTU1MDAwCmxhdGxuZyB7CiAgbGF0aXR1ZGVfZTc6IDM4NDY5NjMyCiAgbG9uZ2l0dWRlX2U3OiAxMTUwMTU2ODAKfQpyYWRpdXM6IDQ3NTA0NDAKcHJvdmVuYW5jZTogNgo=; SIDCC=AJi4QfHkAEuJQkjqHKaVrOSGMBerdz9iiZVsPsE2rw2KWEfGkcMczh3Oo7pwg-Mjmz1EqsE-YrF3; __Secure-3PSIDCC=AJi4QfHUrZjD571gCm5-jqaOQULhDdqmb5ql92leEnpszMcN1eHpL0R-xACOJwmdgoQyIoE1zBBv' \
  --data-raw 'async=translate,sl:fr,tl:en,st:Hello%20There,id:1622317680604,qc:true,ac:true,_id:tw-async-translate,_pms:s,_fmt:pc' \
  --compressed

Which is the endpoint used while on the SERP of Google

It doesn't seems to have a signature.