Community Localizations (v1.0.0.9)

Create a Localization

Grim Dawn reads community localizations from the “/localization” 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
“NL” - Dutch
“PL” - Polish
“RU” - Russian
“ZH” - Chinese
“SK” - Slovak
“PT” - Portuguese
“BG” - Bulgarian
“JA” - Japanese
“VI” - Vietnamese
“TH” - Thai

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.

Item Localization

Gender Support

If you want to make use of gender support, you need to edit tagItemNameOrder (it’s the first tag in “tags_items.txt”) 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 in tagItemNameOrder.

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

If you require it, you can 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.

Conversation Localization

Gender of Target

You can change npc speech in conversations based on the gender of the target the npc is talking to (usually the player) using gender tags.

Hello [[ms]sir[fs]madam], how are you today?

Support for Scriptio Continua

If your language uses scriptio continua and you are encountering text wrapping issues in conversations, add the line “wordmode=false” to your language.def file.

Questions?

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!

Attachment: 1009_english.zip
Attachment: 1010_difference_data_of_english.zip
Attachment: 170722_xpac_skills.zip
Attachment: current version.jpg
Attachment: Language menu.jpg
Attachment: 170820_xpac_skills.zip

Thanks for releasing the new file. :slight_smile: And I noticed that I had overlooked a small change in one conversation (npc_greven.txt).

Many thanks! :slight_smile:

“TT” font set is for Turkish language, right? There is “TT” font set in fonts.arc file; but “TT” is not available in this list. Am I wrong?

@Rhis, any chance that we can translate the main store info (GOG and steam) and the steam achievements?

In this update (Version 1.0.1.0), some conversations, bounties and quest logs were changed besides Text_EN. I think that texts added and changed in v1.0.1.0 are roughly these (attached file). But of course, I’m not able to guarantee it.

I hope that official translation text will be released soon.

Thanks Matougi. Very appreciated to catch up on work. :slight_smile:

Thank you very much!! :slight_smile: I’ve updated my translation based on the file you’ve uploaded. Still waiting for the official version though… :wink:

Thank’s a lot!

Hi, all translators.

As you may know, there were probably only two text changes and additions in this v1.0.1.1 update.

  1. With regard to the conversation of Anasteria, there was no change in my translation due to this degree of change.

  2. One line was added to the tags_ui.txt, but perhaps this is for future expansion and is not currently used. If you know what this line is currently in use, please tell me where it is being used.

  1. npc_outcast_01.txt
    v1.0.1.0: “… So long as Thelon lives, then humanity will never be free of the Aetherial influence.”
    v1.0.1.1: “… So long as Thelon lives, humanity will never be free of the Aetherial influence.”

  2. tags_ui.txt
    v1.0.1.0:
    DamageDurationBleeding= {^E}Bleeding Damage

v1.0.1.1:
DamageDurationBleeding= {^E}Bleeding Damage
DamageDurationElemental= {^E}Elemental Blaze

Hi Matougi,

Thanks for this informations!

wow, DoT for ele dmg? That’s interesting! TYVM Matougi!

Hi, fervent translators.

Eager someone has uploaded the information on new masteries one after another on the web. I got together the texts of the new masteries based on it. And I added the descriptions of the masteries from the Dev Stream.

These sentences may change more or less. However, still it may be quite interesting data at this stage. :slight_smile:

Edit: Deleted old file by update. (22/07)

Hello Matougi

Oh … Thanks! :smiley:

haha, it may be useful for preparation a little, it is still a material of delusion though. :stuck_out_tongue:

Hello, all.

Since the skill of the Inquisitor was revealed with the latest Dev Stream, I updated the file. In addition I added a bit of description about new constellations.

Regarding the new class, it will be helpful here as well.

It would be really helpful (pointed to DEVs) to upload recent texts. There are still people playing the game who are reporting text glitches. Please. Thanks.

Hello Devs!

How is it with the current texts, as Rottenflesh already wrote?

Also the version of the “Grim Dawn Localization Uploader” should set to v1.0.1.0.

And … if it were possible, we could not get from the addon a pre-version of the texts!?

uh, I would like to set the version number to “v1.0.1.1”.

I also hope that text for expansion will be released as soon as possible. Even if there are many uncertain parts, it will be very useful.
Translation takes a lot of time, but our people want a translated version in no time. Nevertheless, the priority to translation of devs is always very very low.

I would like to get the expansion texts out to you ahead of the release, with the obvious caveat that it would include huge spoilers.

How much ahead of the expansion though, I cannot say, as the text is very much still in flux.

As for 1.0.1.1 texts, I realize it’s been a long time since that was released now, oops. Is that something the translation community still needs or have you guys mostly pieced it together at this point?