Board Game Arena

Hi,

would it be possible and reasonable from your side to check if a leading space is present in the translated text also?
It's something that's often overlooked in translations, so i think it would be helpful if you give a hint to translators in this case, similar as you do with trailing spaces.

Hi, do you have an example? It's always more clear with an example

(in general starting with a space should not happen)

Een wrote: ↑19 July 2021, 13:59 Hi, do you have an example? It's always more clear with an example

Here's one: https://boardgamearena.com/translation? ... 24%7Bs%7D)

What's also frequently used (and is annoying to verify) are trailing spaces: https://boardgamearena.com/translation? ... oved%3A%20

Hi,

i have an example from Karawane (engl. Caravan)
https://imgur.com/OO5UOku (i didn't manage to include the sceenshot directly)
The English highlighted text says " Cubes till refill". Before i fixed it, this leading space was missing in the translation.
In the game itself before this text is added a number ranging from 1-4.

Nidhoeggr42 wrote: ↑19 July 2021, 19:39 In the game itself before this text is added a number ranging from 1-4.

The game developper is to blame here, you are not supposed to concatenate translated strings, even with numbers. That could make translations impossible in some langages.
You should probably fill a bug report to ask him to change that.

Thanks for providing examples.
As noted by Tisaac these cases shouldn't happen in principle; the developer should favour substitution to concatenation for translatable strings, and in cases where concatenation is needed (probably almost never, but never say never), the developer should manage spaces outside of the translatable strings.
Still, it's bound to happen, as we have a lot of developers working on games, with various levels of mastery of the framework, which is perfectly normal and a good thing; this kind of strings should be reported as in some cases they can be untranslatable in some languages.
Anyway it's probably good to add a check for leading spaces (we should already have one for trailing spaces if I remember correctly).
Noted for a future release.