[GH-ISSUE #2052] Translations broken in 1.12.7 #588

Open
opened 2026-02-26 18:47:41 +03:00 by kerem · 8 comments
Owner

Originally created by @samuel-cglg on GitHub (Sep 26, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2052

Issue Description

After updating to 1.12.7, I can see some translations broken in the signing invite email.
For example, this is the email the signer user receives after the requester created a signature request (in French):

Image

In the email, the word "sign" should have been translated into "signer" (French).

I guess this was introduced in e547b0b410 and I am afraid it also impacts other places.

Steps to Reproduce

Create and send a signing request in a language other than English.

Expected Behavior

The signing request email content is translated.

Current Behavior

The signing request email has some words not translated.

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

No response

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

  • I have searched the existing issues to make sure this is not a duplicate.
  • I have provided steps to reproduce the issue.
  • I have included relevant environment information.
  • I have included any relevant screenshots.
  • I understand that this is a voluntary contribution and that there is no guarantee of resolution.
  • I want to work on creating a PR for this issue if approved
Originally created by @samuel-cglg on GitHub (Sep 26, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2052 ### Issue Description After updating to 1.12.7, I can see some translations broken in the signing invite email. For example, this is the email the signer user receives after the requester created a signature request (in French): <img width="521" height="624" alt="Image" src="https://github.com/user-attachments/assets/aed6aa93-3897-4051-b275-b90950711b7d" /> In the email, the word "sign" should have been translated into "signer" (French). I guess this was introduced in e547b0b410224696b5cf2a8a5eccff6dde8f89fb and I am afraid it also impacts other places. ### Steps to Reproduce Create and send a signing request in a language other than English. ### Expected Behavior The signing request email content is translated. ### Current Behavior The signing request email has some words not translated. ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] _No response_ ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [x] I have searched the existing issues to make sure this is not a duplicate. - [x] I have provided steps to reproduce the issue. - [x] I have included relevant environment information. - [x] I have included any relevant screenshots. - [x] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [x] I want to work on creating a PR for this issue if approved
Author
Owner

@mKoonrad commented on GitHub (Oct 3, 2025):

I guess this was introduced in e547b0b and I am afraid it also impacts other places.

All new or changed translations are unavailable until translation extraction process is run.

Two days ago, @Mythie manually extracted translations. Previous update of .po file was in August.

Similar problems will continue to occur until the extraction process is automated. This file must be generated every new commit. I hope this process can be improved soon.

<!-- gh-comment-id:3367504566 --> @mKoonrad commented on GitHub (Oct 3, 2025): > I guess this was introduced in [e547b0b](https://github.com/documenso/documenso/commit/e547b0b410224696b5cf2a8a5eccff6dde8f89fb) and I am afraid it also impacts other places. All new or changed translations are unavailable until translation extraction process is run. Two days ago, @Mythie manually extracted translations. Previous update of .po file was in August. Similar problems will continue to occur until the extraction process is automated. This file must be generated every new commit. I hope this process can be improved soon.
Author
Owner

@samuel-cglg commented on GitHub (Oct 6, 2025):

Thanks for the info, I thought there was some automatic process to generate .po files from Crowdin.

I agree that this part should be improved. If not automatic, at least one extraction before releasing a new version would be a good start.

<!-- gh-comment-id:3370084428 --> @samuel-cglg commented on GitHub (Oct 6, 2025): Thanks for the info, I thought there was some automatic process to generate .po files from Crowdin. I agree that this part should be improved. If not automatic, at least one extraction before releasing a new version would be a good start.
Author
Owner

@lucien-klarc commented on GitHub (Jan 5, 2026):

Hi,

Could you please explain in plain english if there is anything i can do to fix this issue?

Thank you very much.
Lucien

<!-- gh-comment-id:3710364110 --> @lucien-klarc commented on GitHub (Jan 5, 2026): Hi, Could you please explain in plain english if there is anything i can do to fix this issue? Thank you very much. Lucien
Author
Owner

@mKoonrad commented on GitHub (Jan 5, 2026):

@lucien-klarc It's solved now.

<!-- gh-comment-id:3711639217 --> @mKoonrad commented on GitHub (Jan 5, 2026): @lucien-klarc It's solved now.
Author
Owner

@lucien-klarc commented on GitHub (Jan 6, 2026):

Thank you @mKoonrad !

<!-- gh-comment-id:3713771292 --> @lucien-klarc commented on GitHub (Jan 6, 2026): Thank you @mKoonrad !
Author
Owner

@lucien-klarc commented on GitHub (Jan 6, 2026):

Thank you again, I can see the pull request however, I am not skilled enough to understand how to have this implemented in my deployment. I am currently using a docker compose with “latest” tag. But as far as I understand, the latest version does not seem to have the fix. How does it work in this event? I apologize for the candid question and thank you for your time!

<!-- gh-comment-id:3714815872 --> @lucien-klarc commented on GitHub (Jan 6, 2026): Thank you again, I can see the pull request however, I am not skilled enough to understand how to have this implemented in my deployment. I am currently using a docker compose with “latest” tag. But as far as I understand, the latest version does not seem to have the fix. How does it work in this event? I apologize for the candid question and thank you for your time!
Author
Owner

@mKoonrad commented on GitHub (Jan 6, 2026):

@lucien-klarc Please check in French web.po file translations for packages/lib/constants/recipient-roles.ts

github.com/documenso/documenso@f6d81b22bd/packages/lib/translations/fr/web.po (L7910-L7913)

It should be "signer" (with a lowercase letter)?

<!-- gh-comment-id:3714928005 --> @mKoonrad commented on GitHub (Jan 6, 2026): @lucien-klarc Please check in French web.po file translations for [packages/lib/constants/recipient-roles.ts ](https://github.com/documenso/documenso/blob/f6d81b22bd3b09c531bada1e647fd525de3bc55b/packages/lib/constants/recipient-roles.ts) https://github.com/documenso/documenso/blob/f6d81b22bd3b09c531bada1e647fd525de3bc55b/packages/lib/translations/fr/web.po#L7910-L7913 It should be "signer" (with a lowercase letter)?
Author
Owner

@lucien-klarc commented on GitHub (Jan 8, 2026):

Hi @mKoonrad,
Thank you my issue is solved !

<!-- gh-comment-id:3722752492 --> @lucien-klarc commented on GitHub (Jan 8, 2026): Hi @mKoonrad, Thank you my issue is solved !
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#588
No description provided.