Internalization and translation without sub- or domain routing. #56515
Unanswered
J4v4Scr1pt
asked this question in
Help
Replies: 2 comments
-
I would love your thoughts about this but for anyone looking in to this, next-translate is truly awesome.
Thats it! (Using App-folder) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for this! Did you find any better solution? Do you still use next-translate? You can have a look at this post, though I haven't tried it myself yet. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
Hello and thanks for this unbelievably good meta-framework! 🚀
A key feature before I can fully move our company to nextJs is the translations. Currently the culture is chosen by the user at a settings page, then saved on the user settings. During initial loading we retrive the user and it's setting where the culutre is. and saves it in redux. On login page the user choose culture that is saved in a cookie.
I thought that translations in nextjs would be the least of my problem moving our application. But after a lot of reasearch I can't find a solution that do not utilze nextJs Internationalization routing.
There are solutions that disguise the url culture path. But it's seems like really clunky and unnecessary solution imo (or in my case at least 😊).
We will use a state manager like Zustand or Jotai to manage the user and it's settings. And when the user changes the culture I will try to use server actions and revalidate the path to update language on the page. In otherwords I will always have access to correct culture in both Client and Server.
After this wall of text, my question is... do anyone know if there is a package out there that dont depend on the culture from the url? That only translates and keeps Client and Server at sync.
Maybe there Is a another good approach to this?
These are libraries I have been looking in to:
https://github.com/aralroca/next-translate
https://www.i18next.com/
https://next-international.vercel.app/
https://github.com/i18nexus/next-i18n-router
https://next-intl-docs.vercel.app/
Would love some thoughts arround this! 🙏
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions