[Feature Request]: Add i18n

[Fghurayri]

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]

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!!

[MrLeebo]

I converted this issue into a discussion because this would be a great feature to have, but it sounds like possible solutions are coming from all different directions. We need to suss out how to best deliver this feature in keeping with i18n standards and Blitz's goals.

[waptik]

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]

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.

[waptik]

@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]

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]

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

[jan-wilhelm]

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

[flybayer]

@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]

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.

[boredland]

I gave that a try, but failed. There's two locations I know of, where next-translate searches for i18n in a static path:
https://github.com/vinissimus/next-translate/blob/master/src/plugin/index.ts#L13
https://github.com/vinissimus/next-translate/blob/master/src/plugin/index.ts#L54

As a first try I just extended that to search inside the app-dir:
https://github.com/finalfinalphotos/next-translate/commit/939b818a005c7f3af07c1ebf39e4f5933d6f2c86

But yeah, that gave me some weird rule-of-hooks validation I didn't understand.

Has anybody already got a working i18n setup yet?

[BjoernRave]

I created an issue on the next-translate repo: aralroca/next-translate#499

[devtombiz]

Any news about this issue ? Do we have a working example of translations in blitz ?

[flybayer]

No news on our side, but latest next-translate should support Blitz. We still have this issue which likely affects some translation libraries.

If anyone has a working example, please PR it to our examples folder!

[devtombiz]

Hi Brandon,
I made a localization example with next-rosetta. It seems to work fine. You can see my PR here: https://github.com/devtombiz/blitzI18nRosetta/pull/1/files
If this is satisfactory to you, then I can create a PR on one of your examples folder (which one ?)
-Tom

[flybayer]

@devtombiz awesome!! Please add to the top level examples/ folder

[devtombiz]

Done, see PR #2872