Implementing internationalization (commonly known as i18n) is often feared by a lot of Front-End developers. Setting it up, adding new languages on...
For further actions, you may consider blocking this person and/or reporting abuse
Happy to hear that you had such a positive experience!
Have you tried github.com/nuxt-community/nuxt-i18n/ by any chance?
I've never had the opportunity to use it, I'll be sure to check it out, thanks for sharing !
If you are using i18n I would suggest disabling the auto translate feature from browsers. I use i18n, in Angular, at work and we have had people get upset about bad translations that after some digging came from google translate and not our translations.
Hi there, we started to used vue-i18n in production here some months ago, it worked pretty good, we just had 2 issues to deal with:
1 - If you use the directive (v-t) translation (still for the front), there is some config to keep the text appearing when using animations.
2 - We had problems with processing the translations in the front after having many lines in each language file, we fixed it bu putting the translation tag on each component and working with it like css and js.
Hi, I have problems to know how to maintan the locale changing routes.