Community Localizations (Build 17)

[Rhis]

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:

“CS” - Czech
“DE” - German
“EL” - Greek
“ES” - Spanish
“FR” - French
“HU” - Hungarian
“IT” - Italian
“KO” - Korean (Build 18)
“NL” - Dutch
“PL” - Polish
“RU” - Russian
“ZH” - Chinese (Build 18)

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 effort!

[Rhis]

B17 Item Tag Change

The first major change for localizations in build 17 is the change to “tagItemNameOrder” in Tags_Items.txt
Build 16 localizations won’t display item names correctly until you update this tag to the following:

tagItemNameOrder={%_s0}{%_s1}{%_s2}{%_s3}{%_s4}

Gender Support

In addition, if you want to make use of gender support, you need to use ‘a’ instead of ‘s’ for the genderized parameters, and specify the index of the parameter which contains the item gender to use for the item.

for example (genderized prefix/quality/style/suffix, with gender chosen by name)

tagItemNameOrder={%_3a0}{%_3a1}{%_3a2}{%_s3}{%_3a4}

Gender codes would then be given to each tag representing an item name. The code present in the name is then used to pick from the genders supplied in other tags.

for example, a masculine singular object would be defined as follows:

tagSword=[ms]Sword

and a genderized suffix would be defined:

tagSuffixPower=[ms]Power[fs]etc[ns]etc

Recognized gender codes are:

[ms] Masculine Singular
[fs] Feminine Singular
[ns] Neuter Singular
[mp] Masculine Plural
[fp] Feminine Plural
[np] Neuter Plural

Reorder All Item Names

If you want to change the order in which item names are built for all items (from prefix/quality/style/name/suffix to some other order), you can change the parameter indexes around.

for example, name/quality/style/prefix/suffix (all items)

tagItemNameOrder={%_s3}{%_s1}{%_s2}{%_s0}{%_s4}

Recapitalize Item Names

If you want to recapitalize the item name string after it is created you can prepend ‘$’ to tagItemNameOrder. The string will be changed so that only the first letter is capitalized.

tagItemNameOrder=${%_s0}{%_s1}{%_s2}{%_s3}{%_s4}

“Godly Plate of the Whale” would become “Godly plate of the whale”.

If you want to mark a specific tag to prevent recapitalization you can prepend ‘$’ to the tag.

tagSuffixWhale=$the Whale

The item name would then become “Godly plate of the Whale”.

Individual Item Tag Reordering (EXPERIMENTAL)

If you want to reorder only some tags, for example to move a certain prefix to the end of the item name, you can prepend reordering info to the tags.

The code is |X where X is from 1 to 9 indicating the new location relative to the locations of other tags.

tagPrefixToBecomeSuffix=|1Warrior's

Tags without reordering info set are considered to have ‘|0’. The tags making up the item name are then sorted in order of their indexes and the item name is created.

In this case, Warrior’s would be moved to the end of the string since all other tags aren’t reordered.

[system]

Oh, so this is why the b16 translation thread was locked, I was looking there for the updated files Thanks a bunch for these, Rhis!

[FOE]

Thanks for the files.

[Lumeriol]

Great work, boys. Lets we go to translated next part of story to our languages

[system]

Thank you very much for the files Rhis, but I am having issues with the genders in the names of the items.

For example the item: Superior Tarnished Mangler should appear in Italian as: Mutilatore Ossidato Superiore

But that’s how the name appears in game:

Invalid Dependency…[ms]Mutilatore Invalid Dependency…[fp]Ossidate[ms]Ossidato[fs]Ossidata[mp]Ossidati Invalid Dependency… [fp]Superiori[ms]Superiore[fs]Superiore[mp]Superiori

That’s how I translated the relevant parts in the tags_items.txt file:

#prefix/quality/style/name/suffix concatenation

tagItemNameOrder={%_a3}{%_a1}{%_a2}{%_a0}{%_a4}

#Weapons

tagWeaponSwordA009=[ms]Mutilatore

#WEAPON_QUALITY

tagQualityWeaponMetal02=[fp]Ossidate[ms]Ossidato[fs]Ossidata[mp]Ossidati

#Prefixes

tagPrefixAO001=[fp]Superiori[ms]Superiore[fs]Superiore[mp]Superiori

Am I doing something wrong?

[Rougecorne]

Thanks.

[Rhis]

Thank you very much for the files Rhis, but I am having issues with the genders in the names of the items.

Try this:

Edit: Failed once again to provide correct info. /removed

[Lumeriol]

Try this:

tagItemNameOrder={%_s3}{%_a1}{%_a2}{%_a0}{%_a4}

I’ll update my terrible instructions.

I have same problem as fbmtt and I used your tag script from first topic, script what you recommended to him and default script - game is still write “Invalid dependency…”.

[system]

Try this:

tagItemNameOrder={%_s3}{%_a1}{%_a2}{%_a0}{%_a4}

I’ll update my terrible instructions.

I have same problem as fbmtt and I used your tag script from first topic, script what you recommended to him and default script - game is still write “Invalid dependency…”.

I can confirm what Lumeriol wrote, I changed the item name order tag and the “Invalid Dependency…” in front of the name is gone now, but not in front of the qualities and the prefixes, which are still all displayed.

To be perfectly clear the in game result is the following:

Mutilatore Invalid Dependency… [fp]Ossidate[ms]Ossidato[fs]Ossidata[mp]Ossidati Invalid Dependency… [fp]Superiori[ms]Superiore[fs]Superiore[mp]Superiori

[Rhis]

Damn it, sorry guys. I forgot one ~minor~ detail. :o

‘a’ params also need to specify the index from which to get the gender information (usually the name)

tagItemNameOrder={%_3a0}{%_3a1}{%_3a2}{%_s3}{%_3a4}

Too many late nights I guess.

Edit: Updating the 2nd post with additional localization features in b17.

[Rougecorne]

A okay !
Thanks

[Rougecorne]

Yeahhh, it worksss !

[system]

Edit: Updating the 2nd post with additional localization features in b17.

Thanks for the instructions, now it works perfectly!

I’m sorry to bother you again but I found a bug when playing the game in Italian: the attack damage numbers above the enemies are not displayed when the “Display Damage” option is active.

[Lumeriol]

I have found small bug in recapitalizated words - if I use the “$” parameter at the beginning of the string, local letters isn’t capitalized and it is staying as small letters. So I have right “Bojový dlouhý meč” but wrong “ďáblův dlouhý meč” instead “Ďáblův dlouhý meč”. Could it be fixed? I don’t know if is this problem only of Czech language or another translations have same “problem”.

[Rhis]

I have found small bug in recapitalizated words - if I use the “$” parameter at the beginning of the string, local letters isn’t capitalized and it is staying as small letters. So I have right “Bojový dlouhý meč” but wrong “ďáblův dlouhý meč” instead “Ďáblův dlouhý meč”. Could it be fixed? I don’t know if is this problem only of Czech language or another translations have same “problem”.

Thanks for the report. I believe this has something to do with system locale settings. Can you check your settings in Windows and try changing to it Czech if it isn’t already set?

This will be fixed in a future build.

[Lumeriol]

Thanks for the report. I believe this has something to do with system locale settings. Can you check your settings in Windows and try changing to it Czech if it isn’t already set?

This will be fixed in a future build.

I am using english version of Windows (original language versions have faster updates and fewer problems), but I have set all locales to Czech - currency, date, keyboard, location, … So problem should be somewhere else?

[Rhis]

I am using english version of Windows (original language versions have faster updates and fewer problems), but I have set all locales to Czech - currency, date, keyboard, location, … So problem should be somewhere else?

Thanks for the info, I’ll download your translation and check it out.

Edit: We’ll be issuing a hotfix patch sometime this week to fix this.

[mad_enis]

I don’t know if is this problem only of Czech language or another translations have same “problem”.

I’ve got this “problem” at russian translate too.

[Lumeriol]

Thanks for the info, I’ll download your translation and check it out.

Edit: We’ll be issuing a hotfix patch sometime this week to fix this.

Thanks for hotfix, I will check it again after release.