search

shadcn-ui / taxonomy

An open source application built using the new router, server components and everything new in Next.js 13.
https://tx.shadcn.com
MIT License
18.39k stars 2.56k forks source link

Internationalization / i18n #56

Open amannn opened 1 year ago

amannn commented 1 year ago

Would you be interested in supporting i18n in this app? I'm the maintainer of next-intl, an internationalization library for Next.js. I just added support for Next.js 13 and the app folder in the latest version (docs).

The latest version includes a drop-in middleware replacement for the i18n routing that Next.js previously provided, but which was removed for the app folder. At this time, Client Components are fully supported by next-intl and support for Server Components is in beta.

If you'd be interested, I could help to set this up in Taxonomy—just let me know!

shadcn commented 1 year ago

Sure. Let me check it out.

Just-Moh-it commented 1 year ago

@shadcn let's have this as a priority, please 🙏🙂

corysimmons commented 1 year ago

Does anyone know if there is a nice/fair comparison table for all the i18n libs out there?

yersultanur commented 1 year ago

I made it work with i18next

If someone interested

link

And take middleware options from js version it works

benyamynbrkyc commented 1 year ago

Any updates on next-intl?

yersultanur commented 1 year ago

Any updates on next-intl?<

better use nextjs built-in internalization options, i18next have issues with client rendering, found this example below, all works pretty good example

benyamynbrkyc commented 1 year ago

Any updates on next-intl?<

better use nextjs built-in internalization options, i18next have issues with client rendering, found this example below, all works pretty good example

Just checked it out, it is pretty good. I see the translations are sourced from JSON files in the dictionaries folder. Is the preferred way of managing these files something like a build step? So far, I've just written scripts to fetch/update the files. Is there another, perhaps more principled way?

yersultanur commented 1 year ago

Any updates on next-intl?<

better use nextjs built-in internalization options, i18next have issues with client rendering, found this example below, all works pretty good example

Just checked it out, it is pretty good. I see the translations are sourced from JSON files in the dictionaries folder. Is the preferred way of managing these files something like a build step? So far, I've just written scripts to fetch/update the files. Is there another, perhaps more principled way?

I don't think so, I made it from his example, but most of it was also written on the beta version of nextjs docs, some must be written, and some can depend on your preference and works pretty well for me. I tried some versions, the best option I found for now is this one. but all of them have issues with middleware, updating public folder files in the app. You just turn off the export config options of the translator and reload the page, and it works fine.

BearCooder commented 8 months ago

Now that next-intl v3 released in Novemver 2023 with stable Server Components support what is the status of this?