Translations update
Posted: Fri Mar 04, 2016 4:16 pm
Just wanted to give everyone a heads up that we have removed the string.Template.substitution implementation in translations.strings.
A few months ago, we added in the string formatting ability. This, for the time being, allowed developers to use either substitution (ie $substitute_name) or string formatting (ie {substitute_name}). We decided it would be best to only have one of these instead of both, as there are compatibility issues that could arise. Since string formatting is a bit more useful (ie using {player.name}, {player.weapon}, {player.language} and only passing in the 'player'), we went with that option.
If you have any translations that use the substitution pattern style, you will need to update them to work for string formatting.
A few months ago, we added in the string formatting ability. This, for the time being, allowed developers to use either substitution (ie $substitute_name) or string formatting (ie {substitute_name}). We decided it would be best to only have one of these instead of both, as there are compatibility issues that could arise. Since string formatting is a bit more useful (ie using {player.name}, {player.weapon}, {player.language} and only passing in the 'player'), we went with that option.
If you have any translations that use the substitution pattern style, you will need to update them to work for string formatting.