bug: Mixed Language Translations in Locale Files

[Yaddalapalli-Charan-Kumar-Naidu]

Describe the Bug

Mixed-language translations are present in two Indian locale files: Tamil (ta-IN.json) and Telugu (te-IN.json).
These files contain text from incorrect languages/scripts (Hindi, Persian/Urdu, Kannada, Malayalam), causing wrong language rendering in the UI and breaking localization consistency.

Steps to Reproduce

1.Open the Rocket.Chat mobile app

2.Change the app language to Telugu (te-IN) or Tamil (ta-IN)

3.Navigate through authentication screens or general UI

4.Observe text rendered in incorrect languages/scripts

Expected Behavior

Telugu locale should display only Telugu (తెలుగు) text

Tamil locale should display only Tamil (தமிழ்) text

All locale JSON files should be syntactically valid

No mixed-language or foreign scripts should appear

Actual Behavior

Telugu locale contains:

Multiple Hindi translations

One Kannada translation

One Malayalam translation

Tamil locale contains:

One Persian/Urdu translation

Incorrect scripts appear in the UI, breaking localization quality

Rocket.Chat Server Version

8.0.0

Rocket.Chat App Version

4.69.0.99999999

Device Name

Realme 12+

OS Version

Android 15

Additional Context

[siddharthchauhan3128]

Hi @Yaddalapalli-Charan-Kumar-Naidu,

I've reviewed the mixed-language issues in the Indian locales. While the current PR addresses Tamil and Telugu, I've noticed that automated translation overlaps often affect other regional languages like Hindi (hi-IN) and Kannada (kn-IN) as well.

I would like to perform a comprehensive audit of all Indic locale files to ensure scripts are consistent and no 'placeholder' translations from other languages remain. This will ensure a much higher quality UI for the entire Indian user base.

Should I submit my findings as a separate PR or collaborate on the existing one?

[Rohit3523]

You can open separate pr for that

[Yaddalapalli-Charan-Kumar-Naidu]

@siddharthchauhan3128 I’ve already audited most of the locale files while working on this fix. Also, just to clarify, there is no kn-IN locale file present in the mobile repo at the moment.

From my review, the mixed-language issue was isolated to ta-IN and te-IN, which is what this PR addresses. If you happen to find any additional inconsistencies in other locales, feel free to open a separate PR as suggested by Rohit