Community Localizations (v1.1.8.0)

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
version=v1.1.0.0

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.

Localizing DLC

Beginning with the release of the Forgotten Gods expansion (v1.1.0.0), the zip file format has changed to include two subdirectories, “fg” (Forgotten Gods), and “aom” (Ashes of Malmouth). Translation files specific to these expansions should appear in these subfolders, and the game will load them appropriately when the expansions are present. This change has been made to allow translations for the base game and expansions to be contained within a single zip file.

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
“TR” - Turkish

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!

community_english_1180_090520.zip (1.2 MB)

8 Likes

Files have been added above.

Hello Rhis,

Thanks for the Datas!

Here are the datas that are changing:
\aom\npc_outcast_03.txt
\aom\tagsgdx1_items.txt
\aom\tagsgdx1_skills.txt
\aom\tagsgdx1_storyelements.txt
\fg\mq_d02_cleansetheusurper.txt
\fg\npc_rover_twinfalls.txt
\fg\object_bridge_areag_arkoviandocks_01.txt
\fg\object_bridgeoldgrove_01.txt
\fg\tagsgdx2_creatures.txt
\fg\tagsgdx2_endlessdungeon.txt
\fg\tagsgdx2_items.txt
\fg\tagsgdx2_skills.txt
\fg\tagsgdx2_storyelements.txt
\language.def
\tags_items.txt
\tags_skills.txt
\tags_storyelements.txt

Thanks, dev team!

A few of small additions to TagsGDX2_Items and TagGDX2_Skills, which I’ve also attached to this post.TagsGDX2_Items.txt (63.3 KB) TagsGDX2_Skills.txt (43.5 KB)

tagGDX2HeadD222=Shattered Realm Ceremonial Mask
tagGDX2HeadD223=Veilkeeper’s Mask
tagGDX2HeadD224=Goredrinker’s Mask
tagGDX2HeadD225=Mask of Ember’s Calling

tagGDX2ShoulderD220=Shattered Realm Ceremonial Mantle
tagGDX2ShoulderD221=Veilkeeper’s Mantle
tagGDX2ShoulderD222=Goredrinker’s Mantle
tagGDX2ShoulderD223=Mantle of Ember’s Calling

tagGDX2TorsoD220=Shattered Realm Ceremonial Armor
tagGDX2TorsoD221=Veilkeeper’s Armor
tagGDX2TorsoD222=Goredrinker’s Armor
tagGDX2TorsoD223=Armor of Ember’s Calling

tagGDX2NecklaceD215=Goredrinker’s Ward

tagGDX2MedalD210=Veilkeeper’s Crest
tagGDX2MedalD211=Crest of Ember’s Calling

tagGDX2ItemSkillD263Name=Keeper of the Veil
tagGDX2ItemSkillD263Desc=You are filled with resolute purpose fueled by the shattered realm’s unstable energies.

As always, we thank the community for your support of the game even after all this time!

8 Likes

Hi there.
I have a question about translating the flavor text of the equipment being added into other languages.

tagGDX2WeaponBluntD209=Totally Normal Guardian
tagGDX2WeaponBluntD209_Desc=“Southpaws be mad.”

This “be mad” means “angry”?

In the literature I read, it is described as follows.
(I’m not a native English speaker, so I’m not sure which one this means)

  • In American English, it means “angry.”
  • In British English, it means “crazy,” “insane,” or “Enthusiasm” or “stupid.”

Correct. Mad = angry. They roughly mean the same exact thing.

The British version of the phrase appears to lean toward a looser or lighter interpretation of this particular phrase but it also works in this case.

“be mad” tends to be used in a joking manner. Kinda like a wink, wink, nudge, nudge way. Half-heartedly.

2 Likes

I greatly appreciate your detailed explanation. :smiley:

Since I don’t live in an English-speaking country,
I don’t usually have the opportunity to learn such detailed nuances.

3 Likes

I have noticed that all of Inquisitor Creed’s entries from the _storyelements.txt were changed from “3rd entry” to “entry 3” and so on. But the tagsgdx1_storyelements.txt still uses “9th entry” and “10th entry”.