Great tut - Thanks Paul! - Not sure if the other videos are out yet (will have a look) - Just a quick one... What would be the best way to store the preferred locale in the cookies, so a returning user will not need to keep updating their lang preferences, then maybe in middleware, redirect based on the cookie?
Hey sorry, I’m not getting notifications in my RUclips app, just saw your comment. So we used to manage this with our own customizations but you end up running into edge cases like “person is on a post, changes language then hits the back button”, it messes with at lot of your flows, when you’ve already got logic for other cases. Not insurmountable but also not worth it when you can just throw one of the popular frameworks we reviewed in video #2 at the problem. The short version: next-intl wins for app router projects in our opinion.
@@rendrdotio thank you for your response. You’ve made some very valid points. As I’m working on an MVP I’ll leave this out for now. But I really appreciate your insight. Have a great day/night depending on your locale 😉
Good stuff! Thank you for putting out content like this one. Nextjs youtubers tend to not talk about localization extensively. Maybe they think it's not sexy, I dunno, but it certainly helped me understanding the basics.
I've just pushed an example here (the repo from video #2) that shows how you can do this without cookies: github.com/rendrdotio/i18n-libraries/commit/0c8015582f68583e5ca7a2e733a44b7535b26172
Great tut - Thanks Paul! - Not sure if the other videos are out yet (will have a look) - Just a quick one... What would be the best way to store the preferred locale in the cookies, so a returning user will not need to keep updating their lang preferences, then maybe in middleware, redirect based on the cookie?
Hey sorry, I’m not getting notifications in my RUclips app, just saw your comment.
So we used to manage this with our own customizations but you end up running into edge cases like “person is on a post, changes language then hits the back button”, it messes with at lot of your flows, when you’ve already got logic for other cases. Not insurmountable but also not worth it when you can just throw one of the popular frameworks we reviewed in video #2 at the problem. The short version: next-intl wins for app router projects in our opinion.
@@rendrdotio thank you for your response. You’ve made some very valid points. As I’m working on an MVP I’ll leave this out for now. But I really appreciate your insight. Have a great day/night depending on your locale 😉
@@davidlintin likewise and good luck with your MVP.
Good stuff! Thank you for putting out content like this one. Nextjs youtubers tend to not talk about localization extensively. Maybe they think it's not sexy, I dunno, but it certainly helped me understanding the basics.
Awesome video. Very clear and detailed. So many videos on that subject on youtube that aren't at this level! 👏
Thank you!
@@rendrdotio I implemented next-international, I like it. Thanks for the suggestion and the video.
Yep, it's tough to argue with. We went with it for our site as well.
Great explanation i love this series it does so much clarification thank you👏🏻♥️
Thanks! Really glad it’s helpful.
What is the extension you use in vscode so that the .json appears with those colors?
Well done Paul!
Thanks my man
Thankyou Sir Perfect Explaination
Too kind, thank you!
Great job!
Thank you!
Very cool video, but one question, why do not use useContext or something similar for the dictionary?
I was watching the video and I had a doubt, why not use next-intl?
how we can update urls also?
How do i store that in cookies? So when i go to other page the value is stored somewhere and it doesnt change back to en.
I've just pushed an example here (the repo from video #2) that shows how you can do this without cookies: github.com/rendrdotio/i18n-libraries/commit/0c8015582f68583e5ca7a2e733a44b7535b26172
@@rendrdotio Thanks! Good luck.
This could have been 5 minutes long. A lot of writing code, that we don't need to watch.
You were not forced to watch I guess. :D