-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I compared this translation with Google Translate, I got a different result. #131
Comments
Hello! Could you share the exact discrepancies, that you've found? |
Hi vitalets, Thank you for the reply. Here is the text in Chinese: The result we have from your library: Google translate's result: You are not probably speaking Thai but the discrepancies can be found in many cases. Text: "How was work today?" The good results are the ones that comes from Google Translate. The incorrect translations are really off, and occasionally they don't make sense. I actually have tried the same examples on another NodeJS library named "@iamtraction/google-translate". The results are identical to yours. I think and according to our users, the discrepancies only started to occur a few days ago. Regards, |
Could you show the code snippet, how do you perform the request? |
The code is copied straight from the npm: The version number is 9.2.1 import { translate } from '@vitalets/google-translate-api'; |
I've tested with russian and confirm the discrepancy. const { text, raw } = await translate(sourceText, { to: 'th' });
console.dir(raw, { depth: null }); |
The same question, I have raised two issues in other repos, I suspect that this is because Google uses different models for different APIs. It seems Google is going to make changes to these undocumented APIs. :( index.js
output:
|
Hi there!
We've noticed some users mentioning a recent dip in translation quality, and I've done some testing myself, comparing your library's results with Google Translate. I've found some discrepancies, with Google Translate sometimes performing better. Any insights you could share on why this might be happening would be greatly appreciated!
Regards,
Thawon Uttamavanit
The text was updated successfully, but these errors were encountered: