MegaGlest Forum
Archives (read only) => Vanilla Glest => Translations => Topic started by: martiño on 2 February 2008, 19:08:05
-
Getting and using Glest translations.
There is a repository of Glest translations here (http://www.glest.org/files/contrib/translations/).
Just download the file you need and unzip it in the core/lang folder of your game, after that the language will become available in the options folder. The default game includes English, Spanish and Galician.
You can use older translations for new versions of the game, however some of the strings will be untranslated.
Making a new translation.
If you make a new translation of the game please send it to us, or post it in this board, and we will upload it.
Please use the following file naming convention: language_version.zip.
Martiño.
-
Please use the following file naming convention: language_version.zip.
Does version relate to the Glest version or the version of the translation?
-
I think thats the same:
english_0.7.2 -> this means, that its a translation for Glest 0.7.2 (which is quite old^^)
Did I make a new post? Maybe I'm sick...
-
:o Thanks Kukac
-
There is a repository of Glest translations here (http://www.glest.org/files/contrib/translations/).
[...]
If you make a new translation of the game please send it to us, or post it in this board, and we will upload it.
ehm... some of them are not here... for example... you know what is missing and i am searching for it :D
-
in wich folder i have to install the german.lng ?
I use a mac
-
I am guessing you go to the place where Glest is installed then go into folder data then lang. Put it in there.
glest/data/lang
-
hello, why i cant translate the name of building, name of unit and some other works (wood, gold, stone, Energy .. etc)and some entries of the unit menu ?
Not already implented ?
Planned for future ?
thx
-
These things are set in the xml files which don't have tranlsation files. If you really wanted to you could change them (/glest/techs/magitech/). Translation files might be implemented in the future.
-
Please use the following file naming convention: language_version.zip.
Is there a naming convention for the file contained in the archive ? It seems that some use language.lng, some use language_version.lng, some use only ascii chars, others use latin-1 chars, etc...
Could you propose a standardization on this matter ? I would love something like isocode.lng, where the ISO code is the official language tag (http://www.langtag.net/whatare.html (http://www.langtag.net/whatare.html)), for example "en" for English, "fr" for French, "pt_BR" for Brazilian, etc.
It is very important that the name of the file does not change between versions, because if the language set in glest.ini does not map to an existing file, Glest will simply refuse to start (IMHO this should be changed too, and default to English for example).
-
Language: Serbian
Author: Drax
E-mail: drax@drax.biz
File: serbian_v3.2.1.lng (http://dramas7.freehostia.com/files/srpski.lng)
-
Hi drax, thanks for the file. Can you put it in a new topic so we can have discussion if we need to (for any future releases anyway)?
Please use the following file naming convention: language_version.zip.
Is there a naming convention for the file contained in the archive ? It seems that some use language.lng, some use language_version.lng, some use only ascii chars, others use latin-1 chars, etc...
Could you propose a standardization on this matter ? I would love something like isocode.lng, where the ISO code is the official language tag (http://www.langtag.net/whatare.html (http://www.langtag.net/whatare.html)), for example "en" for English, "fr" for French, "pt_BR" for Brazilian, etc.
It is very important that the name of the file does not change between versions, because if the language set in glest.ini does not map to an existing file, Glest will simply refuse to start (IMHO this should be changed too, and default to English for example).
I'm fine with this if other people are. The only problem is when you get one that isn't official like leet speak.
http://en.wikipedia.org/wiki/List_of_ISO_639-5_codes
http://www.iana.org/assignments/language-subtag-registry
-
Hi,
I'm new here, german and I hope this is the right topic:
I would like to update the german 3.1.2 translation into a 3.2.1 translation because there is still many untranslated and e.g. the menu shows instead of "Tutorial" "???Tutorial???" (which I wasn't able to found in the language file and doesn't happen with the english language file). My problem is I don't know how to start (maybe a "Get started"-thread might be usefull). On which language file should I base my translation (I don't know whether english.lng works, there are less lines than in german.lng, maybe there is missing something) and is it possible to translate the Unit-Names? If not, when will this feature be included?
Thanks,
pheder
-
The English language files are always up to date. If several lines are missing, it just means they have been removed in the new version. So it's a good idea to base your translation on the current English file. The unit names can only be translated if you modify their XML's.
-
The unit names can only be translated in xml if you modify every reference too - but this not really advisable IMHO.
-
Please ask my Thai language files
I will create your game in the Thai language
email mai_drumpink@hotmail.com
Thank you
-
::)
Hello, maybe could you update the repository with this file https://forum.megaglest.org/index.php?topic=4530.0 (https://forum.megaglest.org/index.php?topic=4530.0)
Sincerely,
cyril