Looks like it's fixed @Dunedan :)

In rP28127#62209, @Stan wrote:

Looks like it's fixed @Dunedan :)

Well, the issue introduced with rP28109 is and the string doesn't look broken anymore in English, but the translations are still not being used in the game.

Sometimes we I release I have to patch a lot of occurences for all mainstream languages. A bit annoying but you gotta do what you can

In rP28127#62214, @Stan wrote:

Sometimes we I release I have to patch a lot of occurences for all mainstream languages. A bit annoying but you gotta do what you can

I'm not sure if I understand you correctly, but if I do I didn't properly explain what's remaining: The remaining problem isn't missing translations in Transifex (because they get "re-filled" from their "translation memory"), but rather the encoding problem with UTF-8 and ISO-8859-1 I mentioned in rP28109.

Ah right I didn't get you. I believe that's because we do something weird with spidermonkey, when we read those files. It might be interesting to see if the engine has different behaviors on different oses with different cultures.
Could also be this https://gitea.itms.ovh/wfg/0ad/src/commit/05e8d14566b49b81f3fcc26a9b8b740a130fe674/source/third_party/tinygettext/src/language.cpp