interpolate variables into translation strings
See original GitHub issueTranslation strings must not be concatenated with variables - the variables need to be interpolated using ICU message syntax
deleteConfirmation: 'Are you sure you want to remove ',
from: ' from ',
still: 'You can still access this account from ',
deleteConfirmation: 'Are you sure you want to delete ',
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Interpolation - i18next documentation
Interpolation is one of the most used functionalities in I18N. It allows integrating dynamic values into your translations.
Read more >How To Pass a Variable to Your Translation String With i18next
Let's learn how i18next interpolation works and how you can use this feature to pass one or more dynamic values to your translation...
Read more >How to use i18n string interpolation - zargony.com
Here, the translation uses string interpolation to put variable values into a meaningful sentence. The translation string itself is a ...
Read more >i18n Attaching variable to translation string - Stack Overflow
I am currently using i18n to translate strings and I'm looking for a way to attach a variable onto the path. This variable...
Read more >Interpolation I (GNU gettext utilities)
Perl is capable of interpolating variables into strings. This offers some nice features in localized programs but can also lead to problems.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Good to avoid it if possible, definitely,at least until we can come up with some better sanitisation on string import.
nope, but searching vue files for these two regexes find some strings with leading and trailing space:
: ' .+',
: '.+ ',
results:
I’d say fixing those is good enough for this task. We could potentially do a deeper audit of all translated strings but I think that’d be overkill at the moment.