SpaceEngineer wrote:Hi guys, thank for offer! You can do translation as like Mosfet said, by simply copying and renaming any existing location file, open it in Notepad++ and starting replacing text lines. Localization files are located in the data/locale/ folder and are named language-gui.cfg
The important thing is that SE uses ANSI encoding, so you must select the code page corresponding to your language in the menu:
code.png
Encoding must be Windows-XXXX. Make sure that your language have such encoding. Languages with more than 128 national characters does not (Chinese, Japanese, Arabic). Currently SE supports only these code pages, because SE needs a pre-drawn font textures to render fonts:
Windows-1250
Windows-1251
Windows-1252
Windows-1254
And you should specify it in the beginning of the locale file:
FontConfig "win1251.cfg"
If you need some other code page, make me know, I can draw one using my Photoshop templates.
Menu textures does not need a translation, in 0.981 they are removed and replaced with a hi-resolution font texture (and the text on buttons are now in the locale file).
Names of a celestial objects are saved in a different file, language-db.cfg, and are more complex to add. Open any existing file to see the format. But you can do this in-game: select an object, open Wiki for it (press [I]), and click "Edit". Enter the name, check the "Real object", type some description if you wish, and click "Save". SE saves changes to language-db.cfg file, making a backup file language-db.bak first. You may revert changes by renaming language-db.bak, but keep in mind that this file got overwritten in the new SE session (ie after restart of SE).
If you are going to edit the language-db.cfg file manually in Notepad++, make sure you setup the same encoding for your language as for locale file language-gui.cfg.
So translating to Arabic isn't possible in Space Engine currently?
CPU: Intel Core i7-6700T 2.8GHz 4-core - Ram: 8GB DDR4 at 2133MHz - 1 DIMM - GPU: NVIDIA GeForce GTX960 4GB GDDR5