An issue with $variables in translated strings
Moderator: Forum Moderators
An issue with $variables in translated strings
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.
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
- Translator
- Posts: 398
- Joined: May 3rd, 2006, 10:23 am
- Location: united europe
Is this still an issue with version 1.3.14 ? Maybe it could be unstickyfied.
http://brilliantanyway.blogspot.com/ Brilliant Anyway
- Viliam
- Translator
- Posts: 1341
- Joined: January 30th, 2004, 11:07 am
- Location: Bratislava, Slovakia
- Contact:
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...
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...
-
- Inactive Developer
- Posts: 787
- Joined: March 31st, 2006, 6:55 am
Re: An issue with $variables in translated strings
As far as I can tell, this isn't an issue anymore.
Re: An issue with $variables in translated strings
I fixed this a long, long time ago.
http://www.wesnoth.org/wiki/User:Sapient... "Looks like your skills saved us again. Uh, well at least, they saved Soarin's apple pie."
Re: An issue with $variables in translated strings
To avoid any more confusion.
Locked.
Locked.
Mainline Maintainer: AOI, DM, NR, TB and THoT.
UMC Maintainer: Forward They Cried, A Few Logs, A Few More Logs, Start of the War, and Battle Against Time
UMC Maintainer: Forward They Cried, A Few Logs, A Few More Logs, Start of the War, and Battle Against Time