We have added a handful of last minute strings, if you have time to update the translation that would be much apriciated.

The translation file is updated and available here: https://raw.githubusercontent.com/diasurgical/devilutionX/master/Translations/de.po

Hm, doesn't seem to work.
I'd be very comfortable with just sending you the de.po file via PM, but you need to change your privacy settings for that or accept a friend request so that i can send you a message.

We are now friends :)

Apparently your work was appreciated :)

:o:o:o diablo 1 Remake Ich liebe euch <3 und auch noch in Deutsch, na jetzt werde ich ganz feucht untenrum zocken zoxken zocken :)<3 das erste mal wo ich diablo 1 gezockt habe, war PS1 und Englisch... Und jetzt deutsch :D<3macht weiter so +1+1+1+1<3<3<3<3<3<3<3 B):)<3

Oh my god, such frenzy. :D
(I'm too perfectionistic myself to join the ecstasy yet, still waiting for a smooth grammar solution... o.O)

Hi, just realised that there are some new lines to translate. I stumbled upon the {1} {2} line - I think this is supposed to be {:s} {:s}? Which format of the two is going to be accepted in the translation?

The format is flexible, it can be "{}" for an value, "{:s}" for string only, or "{:d}" for only numbers. And you can also specify what order you want them by indexing form 0. So "{0} {1}", means first parameter, then second parameter of any type, separated by space. I wrote it like that to make it a bit more clear how it works for translators who need to reorder these. But this is true for all place holder in the translation.

The idea here is to allow translators to change "King's Axe of Speed" in to "Fast Hatchet from Royalty" if that better fits the language model. We will probably also soon change it to "{0:s} {1:s} of {2:s}" to improve on that a bit (the current implementation doesn't allow for having the suffix in the middle).

You can read more about what is supported here: https://fmt.dev/latest/syntax.html

Hey, can someone explain to me again how to test a translation (de.po file)?
Apparently I'm neither able to download the latest version nor to change the language.

Are you referring to 1.3.0 or the latest test build?

Test builds do not currently include contain translations. But if you place the de.mo file generated by Poedit in a folder called "assets" next to deviultionx.exe you should be able to select it from the new in game settings menu.

It worked, thank you.
I'm nearly satisfied with the German translation now. Is there any solution in sight for gender sensitive prefixes?

Still only loose plans for how to handle that.

Well talking is easy but at least for German I'd be happy with an approach that introduces the prefix ending as a forth naming component, so that you have {prefix} {ending} {base item} {suffix}.

In German, prefix endings for the three genders are "er ", "e " and "es ". All prefixes must be truncated in the translation.
As a translator, you will need to translate base items in a way that defines their gender, for example "Axe" becomes "Axt f" and "Helm" becomes "Helm m".
Game then needs to check the ending of the translation and omit the last two letters when using the string.
If base item name ends with " f" and if the item has a prefix and the prefix doesn't end with a hyphen, then apply female prefix ending.

Like that, we can have "Gold-Axt" as well as "Goldene Axt".
As I said, talking is easy, doing is hard. You are probably much more advanced in those considerations, so please be forgiving. ;-)

Can you explain when do you need it to be "Gold-Axt" and when should it be "Goldene Axt"?

We can't encode genders directly in the item name like you suggest, and manipulating the text based on a given languages rules aren't scalable to other languages either. But we have looked in to some options that should be mostly similar in effect.

What we have found so fare is that languages have 1-3 genders, they may or may not be related to sexes (so male/female cannot be used as a general rule). The gender will only affect the translation of the prefix.

Based on that we have considered providing 3 variants of the prefixes and add a discriminator for each item type (preferably just the short name).

This is based on looking at Chinese, English, Korean, Latin, Japanese, Slavic and Scandinavian languages. But crucially we are still missing input for German languages. If you have time it would be helpful if you could drop by the chat sometime.

[context] English -> German

small axe -> kleine Axt
kite shield -> Drachenschild

[axe] neuter -> gender_a
[shield] neuter -> gender_b

[neuter] golden -> golden
[gender_a] golden -> goldene
[gender_b] golden -> goldener

Given the format `{prefix} {item}` this would result in names such as `goldene kleine Axt` and `goldener Drachenschild`. Would that work for German?

If you can implement it like that, yes!

If the prefix is a noun. Some prefixes cannot be expressed as adjectives, so that they need to be connected to the item in a compound noun.
My example with "gold" is misleading because "Gold-" and "Goldene(r/s)" is both possible.

"Jade" or "Schlangen" are better examples. The German language doesn't have corresponding adjectives. That's why you'd go for "Jade-Axt" or "Schlangen-Ring". In other languages you wouldn't notice because you don't need a hyphen there to connect both parts of the compound.

If we use your solution, we have:
[gender_a] kleine Axt
[neuter] Jade-
[gender_a] Jade-
[gender_b] Jade-

Result: Jade-Axt
You would just need to make sure that the game uses the short form [!] because "Jade-kleine Axt" doesn't work.
If that's too tricky I can try to rename those items. I think it's only the small axe and the bows.

This does not bode well. :D
"Armor", "mail" and "plate" are categories which contain both male and female items and atm I don't know how to harmonise all of them.

It's up to to translator then to use short names when translating "Small Axe".
Ok, good to know i guess that's not an option.