#Next 13 and i18n (next-i18next)

1 messages · Page 1 of 1 (latest)

lime obsidian
#

Thanks for pointing it out. If you find anything else on this topic, github issues, documentation, or whatever else, I'd really appreciate if you either shot me a link or message in this thread or if you find some workaround or documentation about. 🙂 I was really hoping I could utilise the new next 13 layout stuff but I can't give up my translations 😦

#

@opal coral
Basically, you have to stick to the usual file structure, apparently they will update the documentation in due time, but nothing yet.
Also, they don't plan on maintaining the locale settings as we've been using them up to now.
Thank you. I hope we could use this thread until there is some open issue or discussion available on github or similar. Please let us know in this thread if you stumble upon anything! I will too.

pearl wadi
#

Cool! I'll see what I can find and will report here! 🙂

opal coral
#

It's quite late here in Europe, so I'm going to go to sleep now, but I've had a look at what is suggested in the new docs

#

And it seems as though they want to push people to use whichever slug you want to for the languages, which is quite ok with me, but seems at first glance quite a bit more work.
I'm going to try to investigate further tomorrow, the implementation might be simple, my fear is that the rewrites and actually including the slugs for all buttons, links and so on could get a bit tedious

#

looking forward to discussing this over here and hopefully finding a way to make it work, I really would like to take advantage of the new app folder, it brings quite a few interesting things to the table at least for my use cases!

lime obsidian
#

@opal coral Much appreciated! I'll have a look tomorrow too. I'm in Finland so it's 2:30am here, indeed time for bed 😅 Talk to y'all tomorrow. Sleep well 🙂

pearl wadi
#

Italy here, time to go to bed 🤣

pearl wadi
#

I am afraid I'm blocked until this is solved (or even acknowledged 😅)

opal coral
#

Yeah, saw that one this morning too

#

From reading the new docs, I think that they will eventually provide guidelines to solve this issue by using middlewares and generatestaticparama

#

I think it will be a mix of using one of those packages to manage the client side with context and the server side will be managed with what I mentioned above

#

We’ll just have to connect both

#

At least that’s my guess, and it does makes sense in my head, that way they just provide guidelines on how to use existing and improved technology, edge functions and don’t create a “fixed” way to do i18n

#

What do you think?

#

Also, the /app directory is not ready for production I think I read

lime obsidian
pearl wadi
#

Yeah I wasn't too comfortable starting coding a PR with no input from the maintainers - it's such a big change.

pearl wadi
lime obsidian
lime obsidian
#

Oh now I saw this: https://beta.nextjs.org/docs/app-directory-roadmap#not-planned-features

Internationalization (i18n)
We will be providing more guidance on solutions for internationalized routing inside app. With the addition of generateStaticParams, which can be used inside layouts, this will provide improved flexibility for handling routing when paired with Middleware versus the existing i18n routing features in pages/.

opal coral
opal coral
#

Just to update anyone that isn't aware of it.
On an issue in the Nextjs repo this preview of the example has been posted by a member of the Nextjs team;:

#

It's not the final form by any means and an actual full example will be provided as stated by leerob in the issue, but for a first idea and some actual code to go by is really useful imo!

lime obsidian