You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
const translate = require('@iamtraction/google-translate');
translate('How was work today?', { to: 'th' }).then(res => {
console.log(res.text);
}).catch(err => {
console.error(err);
});
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 "@vitalets/google-translate-api". The results are identical to yours. I think and according to our users, the discrepancies only started to occur a few days ago.
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: