Skip to content

hi-IN: Adding support for Hindi language (hi-IN) with Devnagri script#3427

Open
akshayadav wants to merge 4 commits intoOpenRCT2:masterfrom
akshayadav:hi-IN_Hindi
Open

hi-IN: Adding support for Hindi language (hi-IN) with Devnagri script#3427
akshayadav wants to merge 4 commits intoOpenRCT2:masterfrom
akshayadav:hi-IN_Hindi

Conversation

@akshayadav
Copy link

This PR includes the addition of a new language file (hi-IN.txt) that contains the necessary translations for the Hindi language.
  • This enhancement will allow users who prefer Hindi to interact with the application in their native language.
  • Improve accessibility and user experience for Hindi-speaking users.

The new language file has been added to the data/language directory, and it follows the same format as other language files in the project.

Changes:

  • The changes include adding two new files
    1. hi-IN.txt
    2. hi-IN.json

Testing:

Screenshots:

Menu In-Game
Screenshot 2026-02-25 at 9 49 11 PM Screenshot 2026-02-25 at 9 53 00 PM
Screenshot 2026-02-25 at 9 48 58 PM Screenshot 2026-02-25 at 9 54 48 PM

…. This commit includes the addition of a new language file (hi-IN.txt) that contains the necessary translations for the Hindi language. This enhancement will allow users who prefer Hindi to interact with the application in their native language, improving accessibility and user experience for Hindi-speaking users. The new language file has been added to the data/language directory, and it follows the same format as other language files in the project.
},
"rct1.scenario_meta.pokey_park": {
"reference-name": "Pokey Park",
"name": "Dinky पार्क",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This suggests you used the US translation for the objects, which is not correct. The source language of the game is UK English. This is particularly noticeable in the names for scenarios, which were changed for the US release of RCT1 for essentially no reason.

Please re-translate the scenario strings using en-GB as the source (which is the language used in the reference_* fields as well).

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Gymnasiast I have updated the hi-IN.json to base off of en-GB.json. My tests are still failing though.
I have added SUPPRESS_WARNING['hi-IN'] = [] to the the .github/workflows/suppress_warning.py as the build fail error suggested.
Anything I'm missing here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants