Community Localizations (Build 31)

Grim Dawn Translations (Archive)
21

Rhis, could you add gender support to the intro? It’s just impossible for me to translate it in a neutral way. :undecided:

22

Why in intro, they speak about IT (Aetheral), not about man or woman. And at the end they speak about neutral human :slight_smile:

23

I’ve found some “tags not found” :
tagShieldB014
tagCharPointSpent
I hope that it helps. Thanks in advance.

24

Another “tag not found”:

tagWeaponCrossbow2hB003

25

Please upload new files ASAP! Gamers are reporting game constantly crashing in some areas / factions as we have no latest files to translate and provide! Thanks.

26

Line 17: the Aetherial says: “Destroy this vessel and I will find another.” It talks about the player character, so it requires genderization.
In portuguese: this vessel = [[ms]este hospedeiro[fs]esta hospedeira]

Line 24: Bourbon says: “This is a human now.” He talks about the player character.
In portuguese: human = [[ms]humano[fs]humana]

Line 28: Bourbon says: “Maybe this one here can still die with some honor.” Again, he talks about the player character.
In portuguese: this one here = [[ms]este aqui[fs]esta aqui]

27

You may override it easily:

  1. Vessel is just vessel, non-genderized box containing the spirit.
  2. Human is just human, no gender specific (like an animal, for example)
  3. “This one here” just replace by “This human” or “This individual here” and you are good to go.

The pain in the *** is step 3, IMHO…

28

I will see what I can do.

The problem is that we don’t have a gender-neutral pronoun and it would be much better to use the gender of the character instead. It sounds a bit strange to use “he” if the character is female, even if this “he” actually refers to the Aetherial.

29

Files updated for v1.0.0.1

30

^^ Thanks!

31

Thanks for release of a latest file!

32

Please add gender to #QualityClass

33

To add gender try playing with triplestringformat tag (SimpleStringsFormat for components, I don´t really remember) in tags_ui, you don’t change #QualityClass, gender works fine.

In spanish order:
SimpleStringsFormat=${%s1} {%1a0}
TripleStringFormat=${%s2} {%2a1} {%2a0}

34

Thank you! I used your format and changed the order, it kind of works. Can you help me some more?

I used this:
SimpleStringsFormat=${%1a0} {%s1}
TripleStringFormat=${%2a0} {%2a1} {%s2}

Everything for items seems fine, except those that don’t have the first part (2a0) are not capitalized and there is a space before the string. Like this:
“Powerful epic armor” and " epic armor".

Same with " component" on items. If it’s a rare component, it’s fine - “Rare component”. And on partial components it doesn’t have gender “[ms]aaa[fs]aaa[ns]aaa[np]aaa partial component”.

I read through the first post again and again but can’t seem to understand how to do what I want. What I know is that if I want to have a gender I have to change “s” to “a”, but what are the numbers before and after it?

35

Ich finde hier nicht mal einen Button , wo ich irgend eine Datei runterladen kann…

36

Im Startbeitrag, ganz Unten, bevor der 2. Beitrag beginnt, z.B.!

Wo “Attached Files” steht …

Aber dies sind hier mal nur die englischen Daten für’s Übersetzen, die deutsche Übersetzung gibt es hier: http://www.grimdawn.com/forums/showpost.php?p=128756&postcount=4 !
(Auch ganz Unten, bei “Attached Files” …)

37

Try this:

tags_items.txt

#ItemComponents

tagComponentIncomplete=[genre]word
tagComponentComplete=[genre]word
tagComponentNumber={%s0 - %d1 / %d2}
tagComponentNumberRare={%1a0} {%s1 - %d2 / %d3}
…
tagEnchanted=[genre]word
tagEnchantmentName=[genre]word

and also these

#ArmorClass
tagArmorClass01=[genre]word
tagArmorClass02
tagArmorClass03

#WeaponClass
tagOneHanded
tagTwoHanded
tagOffHand

#MiscClass
tagRing
tagAmulet
tagMedal
tagBelt

#QualityClass
tagMagic
tagRare
tagEpic
tagLegend

tagStyleUniqueTier2
tagStyleUniqueTier3
tagStyleFactionTier2

Regarding capitalization, I have no idea. Have you tried squeezing a second $ in there before the second term?

38

The second $ does not work, it is shown with the string.

And for components I have
tagComponentIncomplete=[ms]частичен компонент
tagComponentComplete=[ms]компонент
tagComponentNumber=${%s0 - %d1 / %d2}
tagComponentNumberRare=${%1а0} {%s1 - %d2 / %d3}

But the string in game is “%1a0 частичен компонент”. Except for capitalization, its ok for complete normal components, complete rare components, partial normal components. But not for partial rare components.

39

For capitalization, try remove “$”

40

Well that just removes the automatic capitalization, so it’s going to be “Aaaaa Aaaaa” or “aaaaa aaaaa”.