Add I18n support #1570

Closed
opened 2026-04-05 19:35:03 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Lokowitz on 4/25/2025

Community Contribution License Agreement

By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.

Description

After a lot of time reading the documentations i was able to implement a bit of i18n.
But at this stage, I would like to ask you whether you want to proceed in this way.
I choosed next-intl app router without i18n routing.
The language selector is not perfectly integrated i just copied the stuff from the example.
For translation i used Crowdin and performed a machine translation for the top 30 languages, just for testing.
The slected language is stored in a cookie using /src/services/locale.ts maybe it would be better to store this in the user database.

Next steps

If you agree with this way of implementation (next-intl and app router without i18n routing) i would start a new fork of your latest dev branch and maybe wait until you merged all the new stuff you are currently working on and start with a clean branch.

Greetings Marvin

2025-04-25 07_33_50-Window
2025-04-25 07_34_16-Window

*Originally created by @Lokowitz on 4/25/2025* ## Community Contribution License Agreement By creating this pull request, I grant the project maintainers an unlimited, perpetual license to use, modify, and redistribute these contributions under any terms they choose, including both the AGPLv3 and the Fossorial Commercial license terms. I represent that I have the right to grant this license for all contributed content. ## Description After a lot of time reading the documentations i was able to implement a bit of i18n. But at this stage, I would like to ask you whether you want to proceed in this way. I choosed next-intl app router [without i18n routing](https://next-intl.dev/docs/getting-started/app-router/without-i18n-routing). The language selector is not perfectly integrated i just copied the stuff from the [example](https://github.com/amannn/next-intl/tree/main/examples/example-app-router-without-i18n-routing). For translation i used Crowdin and performed a machine translation for the top 30 languages, just for testing. The slected language is stored in a cookie using `/src/services/locale.ts` maybe it would be better to store this in the user database. ## Next steps If you agree with this way of implementation (next-intl and app router without i18n routing) i would start a new fork of your latest dev branch and maybe wait until you merged all the new stuff you are currently working on and start with a clean branch. Greetings Marvin ![2025-04-25 07_33_50-Window](https://github.com/user-attachments/assets/6cc7235b-0252-473e-8801-b60b153eea6e) ![2025-04-25 07_34_16-Window](https://github.com/user-attachments/assets/a7279913-1cf5-454e-a547-1eb5f673fc87)
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1570