ISO 639-2/3
Moderator: OpenTTD Developers
Re: ISO 639-2/3
I can't say for certain (so someone may come along and correct me), but as I understand it, OpenTTD does not use ISO 639 for language codes, rather using the language name as the identifier
The language strings are defined in a text file called, for example and the language is selected in the Openttd.cfg file,
OpenTTD can therefore be translated into any language that can be written using unicode characters. Obviously not every language has been translated, and you'll struggle to find the more obscure ones... but they would all be supported if someone translated the required strings into that language.
TL;DR: As far as I'm aware ISO 639 isn't used to identify languages in OpenTTD, and OpenTTD supports any language that can be written using unicode characters.
The language strings are defined in a text file called, for example
Code: Select all
english.lng
Code: Select all
language = english.lng
TL;DR: As far as I'm aware ISO 639 isn't used to identify languages in OpenTTD, and OpenTTD supports any language that can be written using unicode characters.
Jon
Re: ISO 639-2/3
Okay that sheds some light on my question.
Now to completely make things clear,
Do you accept three letter codes? I notice OpenTTD used two letter codes followed by country code. A language I 'would like' to translate is using a three letter code and has no two letter available, is that possible?
Feel free to correct me
Fromerly known as Alon
Re: ISO 639-2/3
OpenTTD doesn't require the language to be written using a 2-3 letter language code; as audigex mentioned above, it can have basically any name.
Re: ISO 639-2/3
OpenTTD only supports 2-letter codes from ISO-639-1. This is also required by all OpenTTD-related tools.
If audigex and embeddedt provide patches for OpenTTD, Eints, BaNaNaS, ... maybe this can be extended to ISO-639-2/T. Beyond that they probably also have to provide patches for Windows and OSX, not sure whether they would accept
If audigex and embeddedt provide patches for OpenTTD, Eints, BaNaNaS, ... maybe this can be extended to ISO-639-2/T. Beyond that they probably also have to provide patches for Windows and OSX, not sure whether they would accept
⢇⡸⢸⠢⡇⡇⢎⡁⢎⡱⢸⡱⢸⣭⠀⢸⢜⢸⢸⣀⢸⣀⢸⣭⢸⡱⠀⢰⠭⡆⣫⠰⣉⢸⢸⠀⢰⠭⡆⡯⡆⢹⠁⠀⢐⠰⡁
Re: ISO 639-2/3
Found this related issue, it can be used as reference in case someone is interested creating PR(s)
Fromerly known as Alon
Who is online
Users browsing this forum: No registered users and 20 guests