Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request experiments with changing the interpolation for localization.
String interpolation
Instead of passing interpolation arguments through the parameter...
...you will now be able to use string interpolation directly.
Format specifiers
Additionally the format specifiers have changed and now follows the "standard", so to say. While I find
%st
,%do
,%in
or%dt
more straightforward, this change allows the reuse of existing string translations, maybe from an iOS app or similar.So use
%@
for string values,%lld
for int values, and%f
for floating point values.Fallback
If someone mistakenly use the localization initializer without intending to use localization it returns the literal string instead of throwing an error, as requested in #148. The same applies if a string key cannot be found in one of the translation tables, although I leave it open for discussion whether it should return the string key in such cases instead.