vue-i18n
vue-i18n copied to clipboard
intlify
Vue I18n for Vue 3
### Reporting a bug By default when fallbacking fail, two warnings are printed e.g ``` [intlify] Fall back to translate 'bf.headerBar.homeSearchBarPlaceholder' key with 'en' locale [intlify] Not found 'bf.headerBar.homeSearchBarPlaceholder' key...
### Clear and concise description of the problem For some reason, I have to use both Vue composition API and Vue legacy API in my project. I prefer composition API,...
### Clear and concise description of the problem I often stumble upon the problem that I need to localize attributes / props of child components. With the old API I...
### Clear and concise description of the problem According to the docs there are certain special characters (e.g. used for interpolation) which get evaluated by the compiler: https://vue-i18n.intlify.dev/guide/essentials/syntax.html#special-characters Unfortunately this...
### Clear and concise description of the problem In some languages (as german i.e.) there exists the Genitive case in mostly appending a 's' char at the end. So I...
### Reporting a bug? Using `vite-plugin-ssr` to run Vue 3 with server side rendering, leaving the legacy api enabled will cause memory to slowly increase with every request. ### Expected...
If I read the documentation correctly, the Composition API is now the preferred way to use vue-i18n. Whereas using the Options API is considered 'legacy'. I think over time all...
### Reporting a bug? the composable in vue3 for using i18n does not work with the createi18n or the api description is wrong. No translations are found if you create...
### Clear and concise description of the problem I mentioned this in another issue, but decided to create a separate one for clearness. So, I'm organizing my language files as...
### Reporting a bug? in pnpm, the workspace packages are not shredded, and the peerDependencies will not install automatically. which make some problems in the project. https://github.com/pnpm/pnpm/issues/3558 ### Expected behavior...
