An issue with $variables in translated strings

[zookeeper]

If there's a variable used at the beginning of the string, please leave one space at the beginning of the string before the $ sign.

Example:

If this is the original string:
" $ally_name not sure if he trust fish lady."

...then translate it like this:
" $ally_name asdf french gibberisgh qewryty"

...and NOT like this:
"$ally_name asdf french gibberisgh qewryty"

The latter way unfortunately causes some occasionally severe glitches (apparently messing up savefiles and making the string in question invisible in-game). This bug should get fixed sooner or later, of course.

I think we can write a script to automatically check and fix all the existing (mainline) translations for these, though (someone will post back here soon with more information about that), but please remember this at least when you're doing new translation.

[vonHalenbach]

Is this still an issue with version 1.3.14 ? Maybe it could be unstickyfied.

[Viliam]

Too bad we have to think about it.


Maybe it is too late to change this before 1.4, but it would be nice to make some simple unambiguos foolproof system, for example that all variable expressions in strings must be enclosed in {} marks, like:

"{$ally_name} not sure if he trust fish lady."

And then, we would never need this kind of discussion again...

[VS]

Maybe | could work there? It is already used to force variable end...

[SkeletonCrew]

Can somebody test whether it's really still an issue and if so file a bug report at bugs.wesnoth.org? I couldn't find a report there, which makes the odds it getting fixed rather small.

[zookeeper]

As far as I can tell, this isn't an issue anymore.

[Sapient]

I fixed this a long, long time ago.

[Turuk]

To avoid any more confusion.

Locked.