Skip to content

hi-IN: Base file for hindi localisation - #3432

Closed
akshayadav wants to merge 3 commits into
OpenRCT2:masterfrom
akshayadav:hi-IN2
Closed

akshayadav wants to merge 3 commits into
OpenRCT2:masterfrom
akshayadav:hi-IN2

Conversation

@akshayadav

Copy link
Copy Markdown

Base file for the localization support for hindi language

akshayadav280292 and others added 3 commits March 4, 2026 21:46
…anslations

The translation check was failing with a KeyError because hi-IN was not
registered in suppress_warning.py. Also replaced the Polish placeholder
text with actual Hindi translations.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

@tupaschoal tupaschoal left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hi @akshayadav !

This is quite a work, can you walk us through how you approached translating them all? There have been a few new strings in the meantime too, if you want to complete it.

Additionally, if you can rebase so that the CI re-runs it would be great.

Let us know if you need help.

@akshayadav

Copy link
Copy Markdown
Author

Thanks for taking a look, @tupaschoal! To answer your question, this was a first pass where I translated the full en-GB base template into Hindi, but I hadn't set up my workflow correctly against the repo's process, which is why CI kept failing the check always reads suppress_warning.py from master, so no new-language PR can pass CI until hi-IN is registered there
I've requested this on Discord here.

Rather than patching this branch further, I'm going to open a new, proper PR with:
- The branch rebased cleanly on current master
- The strings added since this PR was opened
- Stale entries removed that no longer exist in en-GB
- A couple of translation fixes I found (e.g. STR_1820 had extra text baked into what should be a plain format string)

I'll close this PR out in favor of the new one and link it here.
Thanks for the support!

@tupaschoal

Copy link
Copy Markdown
Member

No problem @akshayadav . As I mentioned on Discord, I already have a PR up to help you with the suppress_warnings, so it shouldn't take long for you to be able to put the new PR up and have it properly validated.

In the meantime, since you said there's going to be a new PR, I'll close this one.

@tupaschoal tupaschoal closed this Sep 26, 2026
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