Currently, the language detection system relies on script and linguistic patterns to identify the input language. As a result, when a user types a sentence in a regional language like Telugu using the Roman (English) script , for example, "nenu vellali" instead of writing it in the native Telugu script , the system detects it as English. This leads to no translation being performed, since it assumes the input is already in the target language.
This limitation affects users who commonly type in regional languages using English letters, a widespread practice in messaging apps, especially on mobile devices. Supporting phonetic or romanized input would greatly improve the usability and flexibility of the translation extension, allowing users to receive accurate translations even when they donβt use the native script.
Expected Outcome:
Ability to detect the intended language from romanized (phonetic) input.
Accurate translation of such input into the selected target language.
Improved user experience for multilingual audiences who mix scripts in conversation.
Use Case Example:
Input: "nenu vellali"
Expected Translation: "I have to go"
(Currently, the system returns "nenu vellali" unchanged)
Please authenticate to join the conversation.
Idea
π‘ Feature Request
UI Kits
Get notified by email when there are changes.
Idea
π‘ Feature Request
UI Kits
Get notified by email when there are changes.