Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Add i18n #279

Closed
Fghurayri opened this issue Apr 26, 2020 · 9 comments
Closed

[Feature Request]: Add i18n #279

Fghurayri opened this issue Apr 26, 2020 · 9 comments

Comments

@Fghurayri
Copy link

What do you want and why?

i18n is immensely needed in any web framework.

Possible implementation(s)

The Nextjs community are yet to agree on the best possible way to implement i18n while keeping SSR / SSG / Serverless working as expected.

Can this be solved by Blitz?

Additional context

vercel/next.js#10651

@flybayer
Copy link
Member

I've never implemented i18n myself, but I agree Blitz should solve this.

So I'd love to hear proposals or ideas on how we should do this!!

@waptik
Copy link

waptik commented Apr 29, 2020

So after going through all possible solutions/examples, with-i18n-rosetta looks like the best possible solution at the moment (demo) . No difficult setup nor extra build steps.
Besides, you can also use your locales as packages and easily import them in your projects like how Uppy does it.

@flybayer
Copy link
Member

flybayer commented Apr 30, 2020

Awesome, thank you @waptik.

So it appears very likely that the Next.js team is working on an official i18n solution (source and source). I think we should wait and see that before doing something ourselves.

Only bummer is they haven't given a timeline.

@flybayer flybayer added status/blocked Waiting on something else and removed status/ready-to-work-on This issue is up for grabs labels Apr 30, 2020
@waptik
Copy link

waptik commented Apr 30, 2020

@flybayer 😱 wow, that's great news 😋. I think an official solution is the best way to go, especially if it's coming from the authors.
So it's worth waiting 😊
Thanks for sharing the good news

@wescopeland
Copy link

A quick update on this: next-i18next now supports serverless i18n from their beta branch. The implementation relies on path rewrites, which are currently behind an experimental flag but will be GA on the next stable release.

@flybayer
Copy link
Member

The Next.js RFC on i18n Routing has just been posted!

@jan-wilhelm
Copy link
Contributor

any news on this, now that NextJS 10 is used in Blitz and includes official support for i18n routing?

@flybayer
Copy link
Member

@jan-wilhelm no news! Now that that's released, it's up to y'all to decide if there's more stuff that we should add on top of that in blitz.

@jan-wilhelm
Copy link
Contributor

After working with "raw" NextJS i18n for a while, I've found next-translate to be a small and very intuitive library for i18n. I would suggest using this for Blitz too, but I am not sure if it works with Blitz's way of moving NextJS pages around. Maybe somebody can try that out? I'm quite busy these days, but could help with that sometime soon.

@MrLeebo MrLeebo closed this as completed Jan 22, 2021
@blitzjs-bot blitzjs-bot bot added status/done and removed status/blocked Waiting on something else labels Jan 22, 2021
@blitz-js blitz-js locked and limited conversation to collaborators Jan 22, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

6 participants