Latest Community Localization discussion - B17 Thread
Build 16 includes community localization support. The build 16 localization file set is attached to this post, in the format used by the game.
Grim Dawn reads community localizations from the “/localizations” subdirectory of the location the game is installed. This is usually similar to “Program Files\Steam\SteamApps\Common\Grim Dawn”. The game reads directly from a .zip file containing your localization files, which can be created using any standard .zip utility.
A community localization consists of a .zip file containing the localization texts along with a “language.def” file which tells the game the name of the localization as well as the font set to use.
example language.def:
language=French
fonts=FR
author=John Smith
The name given in the language field is what shows up in in game options. Community localizations appear as “community_French” for example in the language selection box in game options.
Currently the following font sets are available:
“DE” - German
“EL” - Greek
“FR” - French
“PL” - Polish
“CS” - Czech
“IT” - Italian
“RU” - Russian
“HU” - Hungarian
“KO” - Korean (work in progress)
If you are working on a localization and require a font set for a different language, please PM me the request along with a link to the unicode alphabet for your desired language. We can usually patch new font sets into the game within a few hours.
If you have game related issues with your translation you can post in this thread for help.
Thanks to the community localizers for their hard work!
Can you upload your localization zip file, or email it to [email protected]? I’ll check the umlaut issue out. There isn’t much we can do about the fields being too small at this stage. Perhaps you could adjust those texts somehow?
tagNotFound means one of your localization files is incomplete or bugged in some way. If you can upload the localization zip file I can look into it further.
Make sure you are encoding in UTF-8 without the byte order marker.
If you are using notepad then get notepad++ instead, notepad can’t do it. I’ll probably change build 17 to not care, but for now they have to be saved without BOM.
Workaround is to press enter for skills.txt and move the first entry one line beneath. I also had the Soldier tag missing. Same thing worked for the splash screen. You must have 3 lines.
language=
fonts=
author=
UI works beyond all expectations!
I cannot make the quest system work though…
Edit: Got Notepad++… Oh my God, what have I been doing all this time…
I don’t get how to make it work. Whatever I do, no changes appear in the game. Can someone write a few specific steps on how to make a translation work?
How do I even make the new language show in the options?
Guys, what exactly do you do to make the translation work? I followed what Rhis wrote and no changes I make to the text files show up in the game. I put the zip into the “localization” folder. Rhis wrote “localizations”, but there already was a folder called “localization” (without “s”). I tried to rename it to “localizations”, but that made no difference.
JaseMourne: Get Notepad++ and open language.def (english) and language.def (slovak) side by side.
Enable “show all characters” from Notepad++ and make sure that the lines end in a similar way.
In my case many original NPC files ended with LF while in my own files I had CR. Of course this caused quests and dialogues to be crippled, and tagnotfound popped up in some instances.
and TagNotFound for the “Soldier class”.
