Translations

[katajakasa]

Let's support translations.

• Use the existing DAT format. Filenames [LANGUAGE].DAT for base game translations, and [LANGUAGE]2.DAT for new openomf translations (e.g. ENGLISH.DAT and ENGLISH2.DAT)
• Some sort of source files for each language; then convert automatically in e.g. CI from source format to DAT
• Add Enum to openomf for each translation index so that we can track used strings in code. Only include enum if translation is used (?)
• Add language switch to the configuration menu
• Hunt down all the hardcoded strings in openomf, and move them to the language files.

[wertherhunt]

We have to remind the translators that the tournaments texts are in their respective files, so we have initialy more four files to translate.

[Nopey]

I'd rather not ship modified versions of OMF 2097 assets, or at least not without renaming them to be different.
This seems to be a general rule for this project, as openomf.bk is shipped as an additional file instead of a modified INTRO.BK

A languagetool-based solution would be to ship all 112 strings for languages that aren't english or german in the .LNG2 file, for each tournament that the localization chooses to translate*. To override the logo sprite, a language would specify a .BK file and sprite index.

* I believe localizations should not be required to localize tournaments, but should be technically able to localize any tournament including non-stock ones, matched by file-name.

[Vagabond]

This is my preference as well. I don't think we should ship altered assets in any way.

[Vagabond]

Although I feel like for tournaments, we should ship a single translation file per tournament file. Eg NORTHAM.LNG. This would allow for 3rd party tournaments to also have translations, eg. the Mantis Project.