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
Until yesterday, the translator worked correctly by translating full sentences while preserving context and natural phrasing. However, since yesterday, the translations have become overly literal—each word is translated individually. This results in an output that is unnatural and often incorrect.
Expected Result:
The translator should output a natural, context-aware translation of the entire sentence.
Actual Result:
The translation is produced on a word-by-word basis, leading to a literal translation that lacks natural flow and proper context.
The text was updated successfully, but these errors were encountered:
Same problem for me. I tried to translate "Hello" text from 2 different IP and devices but getting NoTranslationFound error. Before this happens, I was getting really bad translations as you said. IG something wrong with the package for 2-3 days.
Until yesterday, the translator worked correctly by translating full sentences while preserving context and natural phrasing. However, since yesterday, the translations have become overly literal—each word is translated individually. This results in an output that is unnatural and often incorrect.
Expected Result:
The translator should output a natural, context-aware translation of the entire sentence.
Actual Result:
The translation is produced on a word-by-word basis, leading to a literal translation that lacks natural flow and proper context.
The text was updated successfully, but these errors were encountered: