Add support for pluralization locales in component interpolation
See original GitHub issueIn order to avoid having to add markup to translations it would be helpful if component interpolation would also work for pluralization locales.
const messages = {
en: {
comments: 'No comments | {n} comment | {n} comments'
}
}
<i18n path="comments" tag="p">
<b place="n">{{ comments.length }}</b>
</i18n>
Issue Analytics
- State:
- Created 5 years ago
- Reactions:35
- Comments:15 (3 by maintainers)
Top Results From Across the Web
Component interpolation | Vue I18n
Support Version. 7.0+. Sometimes, we need to localize with a locale message that was included in a HTML tag or component. For example:....
Read more >Internationalization in React: Interpolation, Formatting and ...
Any string related specific changes based on locales. Plurals. In this example, we will see the date and string formatting. First, we will ......
Read more >Component Interpolation | Vue I18n - Intlify
Component Interpolation #. Basic Usage #. Sometimes, we need to localize with a locale message that was included in a HTML tag or...
Read more >React localization with i18next - LogRocket Blog
Learn how to localize React apps for an international audience with the internationalization framework, i18next.
Read more >The Ultimate Vue Localization Guide | Phrase
We added router support and opted out of TypeScript when the ... Resource » The Component Interpolation section of the official guide covers ......
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
What about an alternative implementation like:
It feels weird that there’s some significant functionality in this library that you can’t use if you’re using the
<i18n />
tag, unless I am missing something?Something new? It will be so useful.