You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would suggest something more like "donate". Of course all the translation must be adapted as well because in french it really does sound weird to see "Pay to use".
The phrasing "Pay for using Dark Reader" is entirely intentional and aligns directly with both the in-app banner and the contribution landing page:
While Dark Reader remains completely free to use and any financial contribution is strictly voluntary, maintaining an open-source extension of this scale (supporting over 10 million active users across multiple browsers, handling platform migrations, and continuous maintenance) requires significant time and financial resources.
The explicit call to help sustain the project reflects this reality, so the current wording and its corresponding localizations will remain as designed.
I do not speak French myself, so I consulted AI regarding the syntax details. In French, prepositions such as "pour" require an infinitive (pour utiliser), which literal machine translation tools tend to back-translate into English as "to use".
If you have a concrete phrasing in mind that strictly preserves the mandatory "Pay" / "Payer" directive, you are welcome to submit a PR updating fr.config.
Until a concrete PR is submitted, this issue remains closed as intended.
The fact that a translation is grammatically correct does not mean that it is semantically appropriate, which AI fails to understand, making them hallucinate an output. In french, "pour" doesn't necessary requires an infinitive. It could be "Pour L'utilisation"
I quickly checked DR website and I found this line:
Dark Reader is an open source eye-care browser extension. It doesn't send user's data anywhere. Trusted by 10,000,000 users. Developed since 2014. Support us.
I like the wording Support us, it's concise and aligns well with the project, I would translate it as something that is commonly used in French: "Nous soutenir". if we must follow the mandatory "Pay", then "Payer pour l'utilisation de Dark Reader", more correct, but also much longer.
First, apologies for the back-and-forth and any initial confusion. In my daily workflow, I rely on the New Preview design, where these components are hardcoded in English, so I had to double-check where and how this specific locale key is rendered in the classic UI.
For reference, this corresponds to the @pay_for_using key in the locale configs for PL language:
And here is how it actually renders inside the classic extension popup:
As you can see, there are two primary constraints:
Wording intent: As mentioned earlier, retaining the explicit "Pay" directive is an intentional project decision. Softer alternatives such as "Nous soutenir" ("Support us") will not be accepted for this specific call to action.
UI layout limitations:
Current French string: Payer pour utiliser Dark Reader (31 characters).
Polish localization: Zapłać za korzystanie z Dark Reader-a (37 characters) already pushes the button margins to the absolute limit.
Proposed string: Payer pour l'utilisation de Dark Reader (39 characters) adds 2 more characters beyond the Polish text. While it might barely squeeze in, there is a very high risk of text clipping or wrapping onto a second line depending on font rendering and platform scaling.
If you can find a natural French phrasing that preserves the explicit "Pay" directive while staying closer to ~31-33 characters, or if you still want to submit a PR with your 39-character proposal so we can evaluate the visual layout directly in the build, feel free to open one. Otherwise, keeping the current string remains the safest fallback for UI stability.
Quick update: I inspected the classic popup layout via DevTools and injected your proposed phrasing (Payer pour l'utilisation de Dark Reader) into the action button to verify the rendered layout:
As shown in the screenshot, the text fits properly within the button container without triggering any line breaks or clipping.
Please go ahead and submit a PR with this change, and I will proceed with reviewing and merging it.
I am reopening this issue. Please include Fix #16108 in your PR description so that this issue is automatically linked and closed once merged. 😉
Activity
meenphie commentedon Oct 17, 2026
I would suggest something more like "donate". Of course all the translation must be adapted as well because in french it really does sound weird to see "Pay to use".
Myshor commentedon Oct 19, 2026
Hi @meenphie,
Thanks for the feedback.
The phrasing "Pay for using Dark Reader" is entirely intentional and aligns directly with both the in-app banner and the contribution landing page:
While Dark Reader remains completely free to use and any financial contribution is strictly voluntary, maintaining an open-source extension of this scale (supporting over 10 million active users across multiple browsers, handling platform migrations, and continuous maintenance) requires significant time and financial resources.
The explicit call to help sustain the project reflects this reality, so the current wording and its corresponding localizations will remain as designed.
Closing as working as intended.
meenphie commentedon Oct 21, 2026
Got it, but French translation is still wrong, if I translate back to English it becomes "Pay to use", not "Pay for using". That's it.
Myshor commentedon Oct 21, 2026
I do not speak French myself, so I consulted AI regarding the syntax details. In French, prepositions such as "pour" require an infinitive (
pour utiliser), which literal machine translation tools tend to back-translate into English as "to use".If you have a concrete phrasing in mind that strictly preserves the mandatory "Pay" / "Payer" directive, you are welcome to submit a PR updating
fr.config.Until a concrete PR is submitted, this issue remains closed as intended.
meenphie commentedon Oct 24, 2026
The fact that a translation is grammatically correct does not mean that it is semantically appropriate, which AI fails to understand, making them hallucinate an output. In french, "pour" doesn't necessary requires an infinitive. It could be "Pour L'utilisation"
I quickly checked DR website and I found this line:
I like the wording Support us, it's concise and aligns well with the project, I would translate it as something that is commonly used in French: "Nous soutenir". if we must follow the mandatory "Pay", then "Payer pour l'utilisation de Dark Reader", more correct, but also much longer.
If you agree, I'll make a PR
Myshor commentedon Oct 24, 2026
Hi @meenphie,
First, apologies for the back-and-forth and any initial confusion. In my daily workflow, I rely on the New Preview design, where these components are hardcoded in English, so I had to double-check where and how this specific locale key is rendered in the classic UI.
For reference, this corresponds to the
@pay_for_usingkey in the locale configs for PL language:And here is how it actually renders inside the classic extension popup:
As you can see, there are two primary constraints:
Payer pour utiliser Dark Reader(31 characters).Zapłać za korzystanie z Dark Reader-a(37 characters) already pushes the button margins to the absolute limit.Payer pour l'utilisation de Dark Reader(39 characters) adds 2 more characters beyond the Polish text. While it might barely squeeze in, there is a very high risk of text clipping or wrapping onto a second line depending on font rendering and platform scaling.If you can find a natural French phrasing that preserves the explicit "Pay" directive while staying closer to ~31-33 characters, or if you still want to submit a PR with your 39-character proposal so we can evaluate the visual layout directly in the build, feel free to open one. Otherwise, keeping the current string remains the safest fallback for UI stability.
Myshor commentedon Oct 24, 2026
Hi @meenphie,
Quick update: I inspected the classic popup layout via DevTools and injected your proposed phrasing (
Payer pour l'utilisation de Dark Reader) into the action button to verify the rendered layout:As shown in the screenshot, the text fits properly within the button container without triggering any line breaks or clipping.
Please go ahead and submit a PR with this change, and I will proceed with reviewing and merging it.
I am reopening this issue. Please include
Fix #16108in your PR description so that this issue is automatically linked and closed once merged. 😉