-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support i18n custom blocks for Vue SFC #751
Comments
I have the same need |
Saya mengelola berdasarkan cakupan lokal, kompleksitasnya bisa rumit, misalnya, ada beberapa file yang menyediakan terjemahan pada saat yang sama, setiap file memiliki dua bahasa, atau beberapa cakupan digunakan pada saat yang sama const { t } = useI18n({ fallbackRoot: false, useScope: 'local' });
const { t: globalT } = useI18n({ fallbackRoot: false, useScope: 'global' }); |
I'm facing an issue with the locale files becoming too big in my project, so we're looking into using instead, so if we have HelloWorldA.vue HelloWorldB.vue and HelloWorldC.vue they could all get /locales/WorldGreetings.json Unfortunately, both this strategy and inline { ...} will not be detected by i18n ally so this feature would be much appreciated |
Already supported. Just add
|
@kingyue737 , do we need any extra settings except |
same |
Is this fixed? I can't still get it working with |
* fix: add vite-plugin-vue-i18n in framework detection fix #751 * Empty commit to trigger CI --------- Co-authored-by: Alex Terehov <[email protected]>
* fix: add vite-plugin-vue-i18n in framework detection fix lokalise#751 * Empty commit to trigger CI --------- Co-authored-by: Alex Terehov <[email protected]>
Is there a way to support the source path of vue-sfc? <i18n src="./Language.json" /> Reference: |
What framework do you want to have? Please provide links of its i18n solution/package.
@intlify/vite-plugin-vue-i18n
Please provide some overall screenshots about how the i18n usage would be like
Example
Additional context
@intlify/vue-i18n-loader is already supported, so this shouldn't be too much effort.
The text was updated successfully, but these errors were encountered: