Skip to content
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

Next 18 n or i18n #13

Closed
ShintaroNippon opened this issue Nov 28, 2021 · 9 comments
Closed

Next 18 n or i18n #13

ShintaroNippon opened this issue Nov 28, 2021 · 9 comments
Labels
enhancement New feature or request

Comments

@ShintaroNippon
Copy link

ShintaroNippon commented Nov 28, 2021

Hi there. Thanks by the boilerplate.
It is possible to add multi language?
Next 18 n or i18n
And add redux or I should I use context API?

Thanks in advance
Best Shintaro

@ixartz
Copy link
Owner

ixartz commented Nov 28, 2021

Hi @ShintaroNippon,

It's something I want to add the multi language.

Now, most of time I suggest context API instead of Redux. But, it's totally based on you context, sometime you need to continue using Redux.

Thanks.

@ixartz ixartz added the enhancement New feature or request label Nov 28, 2021
@resatyildiz
Copy link

Hi @ixartz,

In my opinion we must add Multi Language infrastructure as base feature in this project so this project will be useful for people. And I want contribute to this project with this feature infrastructure..

Thanks.

@ixartz
Copy link
Owner

ixartz commented May 6, 2022

Totally agree with @resatyildiz, it's definitively useful to add it as a base feature. I'm currently focusing on the testing part by adding Jest, Cypress, etc. As an indie developer, my resources are limited. So, all help are welcome for multi language.

@ixartz ixartz mentioned this issue May 27, 2022
@comverser
Copy link

May I ask you that how this is going now? Was PR #39 not merged because the next-i18next breaks next export? Sorry for asking such a basic question.

@ixartz
Copy link
Owner

ixartz commented Nov 4, 2022

I think the boilerplate should support all features from Next.js. At that time, implementing next-i18next will break next export.
Totally open to any suggestion without breaking any Next.js features.

@ixartz
Copy link
Owner

ixartz commented Nov 4, 2022

I see some library doing the opposite: implementing i18n in next export but breaking other features.

@sunxyw
Copy link
Contributor

sunxyw commented Dec 3, 2023

I'm using ParaglideJS as an i18n solution in my personal project, maybe you could see if it's suitable to be included in this boilerplate.

Documentation: https://inlang.com/m/gerre34r/library-inlang-paraglideJs
How to integrate into App Router: https://inlang.com/g/wxcebbig/guide-lorissigrist-useParaglideJsWithNextjsAppRouter
Page Router: https://inlang.com/g/uxohikde/guide-lorissigrist-useParaglideJsWithNextjsPagesRouter

@ixartz
Copy link
Owner

ixartz commented Dec 3, 2023

I'm actively working to add i18n into the boilerplate using next-intl: https://next-intl-docs.vercel.app

Type-safe, support page and app router, i18n routing, etc. I should release the i18n support in the upcoming weeks.

@ixartz
Copy link
Owner

ixartz commented Dec 8, 2023

Finally, i18n is now official supported in Next.js Boilerplate: #196

Thank you for all your support and feedback.

Also, if you need a translation software, please check out Crowdin: https://l.crowdin.com/next-js
They are now an official sponsor of the project.

@ixartz ixartz closed this as completed Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants