Localisation is one of the ways how to make your project open and accessible for more users.
So I decided to add different languages to my app....
For further actions, you may consider blocking this person and/or reporting abuse
I like i18n although I don't implement it too often in projects I enjoyed reading your process to add such feature.
I have a question, with this setup, is it possible to have next.js figure out the user's preferred language and automatically render the matching language?
Thanks Mateus!
It is actually a good questions. I actually have no idea. I did not build it or did not try. But understand what you mean.
I build just standard always users get on the English page.
Oh that's cool, thanks for replying!
Great stuff here! Love to see you building cool stuff with Next.js.
Thanks Juan. Are you building smth at the moment?
Not anything code related atm. 😅
But building content for folks in SaaS.
That is great! Which type of content? For website or social?
Mostly for websites. Blog content that can then be used for social media and to get more organic traffic. 😀
This is great. Where did you source all your translations? I'm also starting to build a lot using i18next.
I also created a i18next Backend Plugin for those who want to store their translations in a database using Prisma ORM.
Sourcing is all from ChatGPT:)
💪 Great job!
+
++
+++
Awesome job @shnai0 awesome job indeed!!
with this ... i am seeing that i really need to learn NextJS once i am done with python and done with JS. Wooow ... still got a roads to go.
Thanks Lionel!
It seems that it pretty simple language and very clear one.
I don’t know python:) maybe I should also look into it:)
AWESOME!
Thanks Leandro 😊
ch == Switzerland (derived from Confoederatio Helvetica)
cn == China
Omg
Thank you for noticing that Gutem. I was kind of confident it is like that. Need to push update for it.
Nice work
Thank you Ahmad!
Hello Iuliia. By any chance did you explore how i18n could pull latest translation content from an API? Not just on first launch, but on subsequent navigation or page refresh to always refer to latest translated content from backend.