Refactor translation configuration to support i18n with keys and EN/R… #102
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
How were the translation keys generated or was it all done by hand? if you used a tool do you know if there is a way you can influence what the keys are named? (idealy |
Closed
KohKaiSern
added a commit
to KohKaiSern/GregTech-Modern-Community-Pack
that referenced
this pull request
Jul 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR refactors the existing configuration to use translation keys instead of hardcoded text values. It introduces full support for internationalization (i18n), enabling switching between English and Russian translations.
Changes include:
en_us.json) and Russian (ru_ru.json).This update improves maintainability and prepares the app for supporting additional languages in the future.