Skip to content

Conversation

@Alexxcuh
Copy link

@Alexxcuh Alexxcuh commented Aug 6, 2025

No description provided.

@opekope2 opekope2 added the translation Addition or modification of OptiGUI supported languages label Aug 6, 2025
@opekope2
Copy link
Owner

Hello!
Thank you for your patience — I was working on updating the translations, which took more time than I expected. I updated the translations on the dev branch with over 70 new translations.
If you want to submit updated translations for the next OptiGUI 3 alpha release, you have at least 30 days.

@Alexxcuh
Copy link
Author

Alright

@opekope2
Copy link
Owner

After implementing more features, I had to make some minor changes to the translations.

After skimming through the translation file, I have some suggestions:

  • optigui.validation.error.empty_map is not capitalized (typo?)
  • optigui.rp_converter.convert_properties: OptiFine uses the .properties extension, but it can stay like how it is
  • For optigui.rp_loader.warn.no_interaction_target, I didn't provide enough context. blocks, entities, items, inventory, and unknown will be part of V2 JSON resources (just like texture.PATH in OptiFine properties):
    {
      "blocks": [],
      "entities": [],
      "items": [],
      "inventory": false,
      "unknown": true
    }

@opekope2
Copy link
Owner

opekope2 commented Nov 7, 2025

The translation keys for OptiGUI 3 alpha 4 are finished, no more additions, maybe small clarifications.
I organized the translation keys since your last revision, so some of them may be out of place. Other than that, 12 translations are missing.
See my previous comment for some clarifications.
You have at least 30 days to update your translation.

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

Labels

translation Addition or modification of OptiGUI supported languages

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants