5. Add New Language

5.1 What is this?

This step allows you to add a new language (like Hindi, Tamil, Punjabi) to your CRS system so users can view the application in their preferred language.

5.2 What you need

Item	Description	Example
Gateway URL	Your system's gateway URL	https://qa.digit.org
Username	Admin username with MDMS_ADMIN role	MDMSADMIN
Password	Your password	********
State Tenant ID	State-level tenant code	pg
Target Tenant IDs	Cities where you want the language	pg.citya, pg.cityb
Language Name	Display name for users	Hindi
Locale Code	Language code	hi_IN

5.3 Common locale codes

Language	Locale Code	Native Name
Hindi	hi_IN	हिंदी
Tamil	ta_IN	தமிழ்
Punjabi	pa_IN	ਪੰਜਾਬੀ
Bengali	bn_IN	বাংলা
Telugu	te_IN	తెలుగు
Marathi	mr_IN	मराठी
Gujarati	gu_IN	ગુજરાતી
Kannada	kn_IN	ಕನ್ನಡ
Malayalam	ml_IN	മലയാളം
Odia	or_IN	ଓଡ଼ିଆ
Assamese	as_IN	অসমীয়া

Format Rule: language_COUNTRY

• language = 2 lowercase letters (hi, ta, pa)

• COUNTRY = 2 uppercase letters (IN)

---

5.4 Fill in translations

Open the downloaded Excel file, you will see these columns:

Module	Code	Locale	Message
rainmaker-pgr	PGR_COMPLAINT_TYPE_GARBAGE	hi_IN	(empty - fill this)
rainmaker-pgr	PGR_COMPLAINT_TYPE_WATER	hi_IN	(empty - fill this)

Fill the "Message" column with translations:

Example translations (Hindi):

Code	English Meaning	Hindi Translation
PGR_COMPLAINT_TYPE_GARBAGE	Garbage Collection	कचरा संग्रहण
PGR_COMPLAINT_TYPE_WATER	Water Supply	जल आपूर्ति
COMMON_SUBMIT	Submit	जमा करें
COMMON_CANCEL	Cancel	रद्द करें

Important Rules:

✅ DO	❌ DON'T
Translate ALL messages	Leave any cell empty
Use native script	Change Module, Code, or Locale columns
Keep placeholders like {0}, {1}	Add or delete rows
Save the file	Change the sheet name

About Placeholders:

If you see {0} or {1} in English, keep them in your translation:

English	Hindi
Welcome {0}, you have {1} complaints	स्वागत है {0}, आपके पास {1} शिकायतें हैं

Save the file when done (Ctrl+S or Cmd+S) and upload in the notebook directory.

---

5.5 Upload the translations file

Upload the updated Excel back into the notebook directory. Use the upload cell shown in the notebook.

5.6 Process the data

5.7 Verify ingestion

5.8 Verify in application

Step 1: Open your CRS application and login

Step 2: Login to one of your target tenants (e.g., pg.citya)

Step 3: Find the language selector (usually in the header)

Step 4: Click the language dropdown

Step 5: Select your new language (e.g., Hindi)

Step 6: Verify the translations appear

What to check:

Area	What Should Change
Complaint Types	कचरा संग्रहण instead of Garbage Collection
Buttons	जमा करें instead of Submit
Menu Items	All navigation in Hindi
Form Labels	All field names in Hindi
Error Messages	All errors in Hindi

5.9 Troubleshooting language issues

Problem 1: Language not in dropdown

Cause	Solution
Tenant update failed	Check upload output for errors
Wrong tenant login	Login to target tenant (pg.citya)
Browser cache	Clear cache and reload (Ctrl+Shift+R)

---

Problem 2: Translations not appearing

Cause	Solution
Upload failed	Check for "Failed: X" in output
Cache issue	Wait 2-3 minutes, clear cache, reload
Logout and login again	Sometimes session needs refresh

---

Problem 3: Some text is still in English

Cause	Solution
Empty cells in Excel	Check and fill missing translations
Module-specific messages	Contact IT for additional translation keys

---

5.10 Updating existing translations

To update translations for a language you already added:

Step 1: Run "Fetch Data" again with the same locale code

Step 2: The Excel will show your existing translations

Step 3: Edit the translations you want to change

Step 4: Upload the file again (Steps 5.6 and 5.7)

The system will update (not duplicate) the messages.

---

5.11 Adding language to more cities

To add an existing language to new cities:

Step 1: Run "Fetch Data" with new Target Tenant IDs

Example: pg.cityc, pg.cityd

Step 2: Use the same locale code (e.g., hi_IN)

Step 3: Excel will show existing translations (no need to re-translate)

Step 4: Upload the file

Only the tenant configuration will be updated.

---

5.12 Language upload checklist

Use this checklist to track your progress:

Authentication

• Gateway URL entered correctly

• Username and password correct

• Authentication successful

• Fetch Data

• Target Tenant IDs entered

• Language name entered

• Locale code entered correctly

• Excel file downloaded

Translation

• All messages translated

• No empty cells

• Placeholders {0}, {1} preserved

• File saved

Upload

• File validated successfully

• Messages uploaded (0 failed)

• Tenants updated (0 failed)

Verification

• Language appears in the dropdown

• Translations display correctly

• Tested all major screens

• Tested on mobile

5.13 Best practices for translation

Quality Tips:

✅ Good Practice	❌ Avoid
Use professional translators	Rely only on Google Translate
Keep terminology consistent	Mix formal and informal tone
Have native speakers review	Deploy without review
Test with real users	Skip user testing