[GH-ISSUE #202] Localization #61

Closed
opened 2026-02-26 18:45:11 +03:00 by kerem · 5 comments
Owner

Originally created by @david-loe on GitHub (Jun 9, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/202

Localization would be nice to have, especially considering the date printed on the documents.

Originally created by @david-loe on GitHub (Jun 9, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/202 Localization would be nice to have, especially considering the date printed on the documents.
kerem 2026-02-26 18:45:11 +03:00
  • closed this issue
  • added the
    Stale
    label
Author
Owner

@Mythie commented on GitHub (Jun 17, 2023):

Completely agree, while it might not be v1.0 I'd be aiming to do so in quick succession with it likely appearing a v1.1 release.

Given that we will now be using Next13 with AppDir, I'm wondering if anyone has any cool suggestions for localization providers? I don't think we need to go down the NextIntl path and I'm not even sure if it's available yet for AppDir projects.

<!-- gh-comment-id:1595590482 --> @Mythie commented on GitHub (Jun 17, 2023): Completely agree, while it might not be v1.0 I'd be aiming to do so in quick succession with it likely appearing a v1.1 release. Given that we will now be using Next13 with AppDir, I'm wondering if anyone has any cool suggestions for localization providers? I don't think we need to go down the NextIntl path and I'm not even sure if it's available yet for AppDir projects.
Author
Owner

@nsylke commented on GitHub (Aug 17, 2023):

I normally go with i18next for localization, there is a couple ways it could be implemented, using routes to determine the language (/en/dashboard, /de/dashboard, etc.) or could use the Context API from React to allow the user to select the language without changing the route. Probably best to default to the Accept-Language header on either option.

Happy to implement the base of this and localize all current messages through the dashboard.

<!-- gh-comment-id:1681479885 --> @nsylke commented on GitHub (Aug 17, 2023): I normally go with [i18next](https://www.i18next.com/) for localization, there is a couple ways it could be implemented, using routes to determine the language (`/en/dashboard`, `/de/dashboard`, etc.) or could use the Context API from React to allow the user to select the language without changing the route. Probably best to default to the `Accept-Language` header on either option. Happy to implement the base of this and localize all current messages through the dashboard.
Author
Owner

@anikdhabal commented on GitHub (Nov 20, 2023):

Hey @catalinpit @Mythie Can you assign me? I am willing to work on this.

<!-- gh-comment-id:1819801510 --> @anikdhabal commented on GitHub (Nov 20, 2023): Hey @catalinpit @Mythie Can you assign me? I am willing to work on this.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 21, 2023):

This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

<!-- gh-comment-id:1865297234 --> @github-actions[bot] commented on GitHub (Dec 21, 2023): This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected
Author
Owner

@github-actions[bot] commented on GitHub (Dec 28, 2023):

This issue has been closed because of inactivity.

<!-- gh-comment-id:1870918122 --> @github-actions[bot] commented on GitHub (Dec 28, 2023): This issue has been closed because of inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#61
No description provided.