The Connect Forum encourages users to write posts or replies in their languages.
Others can refer to that in English.
Earlier, @MukulR highlighting errors in translation of Bengali in this post.
And the solutions stated : posts written by Local Guides are translated by Google Translate and not by Connect**.**
Yesterday, I wrote a reply in Marathi.
A side-by-side comparison of that in Google translate is as underneath.
I find GT has done the job to 99% accuracy and contains only two insignificant errors.
However, when I refer to the translation of the same text on Connect as in the screenshot below, there are disgusting errors in that.
If Google Translate represents the exclusive origin for that, why there is a difference in translation when the source language text is the same at both the places? Even the syntax of question is also incorrect!
Further, when the original post is in English, comments in any other language are automatically translated incomprehensibly, and that is likely to create an aversion.
Is there any solution to avoid that?
If you use Chrome to translate the page what is the outcome (translate button in the address bar) - is it similar to Connect or similar to the translate web page?
I’m only guessing here but my expectation is that the API version is reliant on correctly detecting both the language and dialect where the Google translate UI can take hints from the user. I see you’ve told it to use Marathi, if you leave the translate UI on auto does it give the same outcome as Connect?
I still think the difference to translate being able to automatically detect the language @C_T in your example you set the language, in Connect it must automatically detect.