#i18n's k_round key is used in a way that makes accurate translation impossible in some language

8 messages · Page 1 of 1 (latest)

worn jacinth
#

We discovered while improving the French translation through a mod that the k_round key, that simply reads "Round" in English, is used at least in two places in the UI.

It is problematic in that case, as we would need to have a specific key for the usage in the Round score sentence: it would not be translated by a concatenation of the translation of Round and of score without reading really weird in French (Manche score is not a thing; Score de la manche would be).

Ideally, we would have a k_round_score label (with two lines, like other i18n keys that work like that) to translate it better, and keeping k_round as Manche for all the other three usage of this term through the UI.

formal saffron
#

This is an issue with "run info" too, I believe

#

Because of how wonky it is translated into russian

#

Quite a few strings are being reused in multiple places which does not work with languages other than English

nimble pollen
#

No there is two distinct fields for Run Info

b_run_info_2 = "Info",```
formal saffron
#

I see

nimble pollen
#

Here the "score" word below Round is in the k_lower_score key. But the k_upper_score key is missing, it's the k_round key used instead

worn jacinth
#

I think that localthunk idea behind k_lower_score was "score but in lowercase", maybe foreshadowing other usage somewhere else; but to be fair, to our knowledge, it's the only time it's used through the codebase