Closed Bug 1185991 Opened 10 years ago Closed 10 years ago

[fr] Input: untranslated strings: 2015-07-21

Categories

(Mozilla Localizations :: fr / French, defect)

Product:
Mozilla Localizations
Component:
fr / French
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: willkg, Assigned: bugzilla.fr)

References

Details

There are strings that need to be translated for Input <https://input.mozilla.org/>. 6 strings consisting of 49 words These strings cover changes to the Thank You page template to make it product-agnostic. Input strings can be translated in the Input project in Verbatim <https://localize.mozilla.org/fr/input/>. Once those are translated, we can pick up all the recent changes in fr. Thank you for your work on Input! Your work helps thousands of people help us understand how we can fix Mozilla products to make them better for everyone. If you have any questions, please let us know.
The missing strings have been pushed from Verbatim. I don't know how long it will take for them to appear on the website though.
Thanks for taking this one, Benoit :) If it's like for Bug 1104777, Will can handle the push to production.
The strings are in the codebase, but not available to be seen because the current Thank You page with the old strings is still live. However, I updated the .po files locally, compiled the .mo file and took a screenshot of what it looks like with your strings changes: http://bluesock.org/~willkg/images/link/fr_thanks_screenshot.png Does that look good to you? If so, they'll go out with the next deploy I do, but they won't go live until I finish bug #1172019.
Changes looks good, but where does the %product variable come from? "Firefox for Android" should actually be "Firefox pour Android" in French, but I'm not sure where it can be changed.
It comes from the database. Translating content from the database is covered in bug #1001430.
This is done. It's not pushed out, yet, but I'm going to mark it FIXED anyhow. If that breaks your workflow, feel free to re-open. Thank you!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.