Community Localizations (v1.0.5.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.0.4.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.

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!

Hello,

Thanks for the support!

Thank you for uploading in advance. :slight_smile:

bq_cu14.txt

Bounty: Connivius Earthshell

Instead of this it should be “Ragarroth the Tormented” in Bounty name.

There are missing Crucible lines (this bug was in 1.0.4.0 version also). See that post for fix: http://www.grimdawn.com/forums/showpost.php?p=592954&postcount=19

The files of Russian localization are ready, we are waiting for the update.

Minor update to the following tag in TagsGDX1_Skills.

tagGDX1CompSkillA109Desc=Hurl a blade coated in caustic acid that spins outward away from your position, piercing through all enemies along the way before returning to you.

And in Tags_UI, was missing a space at the beginning.

ImprovedTimeFormat= {^E}with {^H}{%+.0f0}% {^E}Increased Duration

The error pointed out above in Bounty BQ_CU14.qst will also be addressed for the release.

Thanks for the additional information.
Japanese version can be released at any time! :slight_smile:

What about “unofficial fix” of missing tags_survival2 and npc_event_0x files (http://www.grimdawn.com/forums/showpost.php?p=592954&postcount=19), there are old values or “fixed” values are right?

In 1050 zip file are old files.

Will be there a new zip file with all fixes? :slight_smile:

@Rhis, @Zantai, looks like there’s a little bug with the download interface:

EDIT: Solved. Thanks

Hello Rhis,

A question to Crucible:

In the zip file here in the thread are the files …

  • tags_survival.txt
  • tags_survivalui.txt
    … for Crucible.

In the Text_EN.arc file under “Grim Dawn\survivalmode1\resources” is only the file …

  • tags_survival2.txt
    there!?

Is this file “tags_survival2.txt” needed?!

There’s only 2 tags in that file.

One is unused and the other is a proper noun (NPC name).

OK, thanks.

Another things see please here: http://www.grimdawn.com/forums/showpost.php?p=620582&postcount=16 !?

Not sure how likely those things are to happen, I’m afraid.

What sort of info are you looking to include with the translation?

You could consider adding it to the starting tutorial.

OK.

Information for the translations!

That the translation is for the game with or without addon and so things.

That we do.

But the text is only show for some seconds, see pic. in the corner left on top (Text "HINWEIS: …).

Maybe this issue could be fixed by adding a tag to each row of dialogue? Is that a possibility? Otherwise I think we’d have to upload three different translations (one for the base game, one for the base game + AoM, and in the future one for the base game + AoM + FG). But I’d need you guys to provide me with the necessary files (base game, base game + AoM, base game + AoM + FG) because I don’t know how to extract all these files in .txt format myself. :undecided:

Yes!

That is what I also have addressed in my link #1