feat: Add f_lang function to emulate python f-strings for translations #5962
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.
Fixes #5961
From a discussion with @alexgarel who suggested python's f-strings.
This is to make it possible to use named variables in translations.
e.g. "blablabla {some_variable} blabla {some_other_variable} bla."
Benefits:
For existing strings, I think we can keep the %s for now (unless there's a good reason to change them), so that translators don't have to retranslate them.
For new strings, I think named parameters is better.