Discrepancy with Google Translation

[AdamElitzur]

Discrepancy with Google Translation

[AidanWelch]

@AdamElitzur Yep you got it exactly right! I'm glad that solution works for you!

[AidanWelch]

I'm glad you're liking it! My immediate guess would have been that it was because of forceBatch but you already set that to false so I'd have to investigate. I'll try to take a look when I get a chance soon (If I take too long feel free to @ me)

[AdamElitzur]

Thanks so much! Let me know if you find anything, and if it's happening on your side or not.

[AdamElitzur]

@AidanWelch I hope all is well! Finding anything yet with the discrepancy? Anything else I should try in the meantime? Thanks so much.

[AidanWelch]

Well, the issue is with batch translation as

translate('ארים ראשי, אשא עיני אל ההרים במרחקים', {from: 'he', to: 'en', forceBatch: false, fallbackBatch: false}); // => res.text === 'I lift my head, I will lift my eyes to the mountains in the distance'

However that responds with Error: Too Many Requests sometimes. So, it must just be more aggressive rate limiting. With fallbackBatch: true when singleTranslate fails then batchTranslate is called rather than throwing an error. But, to be honest, it might have been a mistake on my part to degrade translation quality rather than throw an error by default.

Basically, forceBatch: false and fallbackBatch: false must be set to force the more accurate singleTranslate.

[AidanWelch]

@AdamElitzur (Just pinging in case you didn't get the notification)

[AdamElitzur]

Thanks so much @AidanWelch! If I set forceBatch: false and fallbackBatch: false, then could that cause errors if there are too many requests?
I would like for a translation to show no matter what, even if the quality is worse, if that is the best possible outcome (better than an error). So actually, I like your move to degrade translation quality rather than throw an error by default! Thank you!