Arnon R.
Arnon R.
I believe the best solution would be to add the i18n package and each of us would do an individualized translation for each language. It's the most work, but it's...
Support for `.js` within `.vue` would be very welcome. Really very useful!!
Has same problem. Solved changing from vue-cli to Vite. (ps.: only did this because I am working in a very small repo)
If the repository worked with i18n, I would be very happy to translate it to Portuguese. @gskinner think about it.
Amazing merge! Does this mean that we now have open doors for other languages? @KimYangOfCat, can we have some README.md with basic instructions for adding other languages?
Right, but they will be in the language dropdown of the main site (https://pinia.vuejs.org/) or it will be another url.
The [solution](https://github.com/kazupon/vue-i18n/issues/474#issuecomment-444817451) of @dekadentno helped me a lot!! I have a similar issue so I decided to use this one instead creating another one. Here is: I have an Settings...
Maybe, it is better to work on a fork: https://github.com/openscript-ch/i18n-ally-fork/issues/1
@BernhardSchlegel, if you using it in `vite.config.ts` try this: ```ts import VueI18nPlugin from '@intlify/unplugin-vue-i18n/vite' import vue from '@vitejs/plugin-vue' import { fileURLToPath, URL } from 'node:url' import path from 'path' import...