Question: contributing additional Save Editor UI locales via ARB

[AleksSmash2019]

Hello dh0er,

I would like to ask about contributing additional UI translations for GORE Save Editor before creating any files or publishing anything.

The public source is MIT-licensed, and the Save Editor already has a real Flutter localization architecture under apps/save-editor/lib/l10n, with ARB resources and generated localization code. The current generated contract lists German, English, Spanish, French, Italian, Japanese, Polish, Portuguese, Brazilian Portuguese, Russian, Chinese and Simplified Chinese. I noticed that languages such as Ukrainian, Korean or Turkish are not currently listed, although the Gothic Remake ecosystem has users of those languages.

Would you be willing to accept a source-level localization contribution for one or more missing locales? I would preserve all existing keys and placeholders, add only new translation values, keep the MIT copyright/license notices, disclose that the translation text was AI-assisted, and submit the work as a pull request or in whatever source workflow you prefer. I would not distribute a rebuilt executable, a standalone ARB file, or a separate Nexus translation page unless you explicitly confirm the supported packaging and release method.

Could you please advise:

1. Which missing locale would be useful and acceptable for the project?
2. Should the contribution be a pull request adding app_<locale>.arb and generated resources, or do you prefer to run code generation and integrate it yourself?
3. Are AI-assisted translations acceptable if they are clearly disclosed and reviewed for placeholders, terminology and consistency?
4. Do you want the contribution credited under the existing project copyright and MIT notice, and should the Nexus page mention your preferred source/release path?

I will not create or publish a translation until you confirm the workflow. Thank you for building this tool and for making the source available.

Best regards,
AleksSmash2019

[dh0er]

Hi AleksSmash2019,

thank you for asking, and of course you can contribute! Game texts would be english for new languages but all the UI texts can of course be translated.

To answer your 4 questions:

1. Whatever language you like or think makes sense
2. A pull request with the arb files only would be best, I would do the integration
3. This project is 100% AI coded, so yes of course
4. No need for a separate project or Nexus page

Daniel

[dh0er]

Just thought about that again. I would rather let users freely choose both language of game texts and UI texts. So e.g. Ukrainian users can have ukrainian UI with Russian game texts, or sth like that.