Closed
Bug 1305778
Opened 8 years ago
Closed 8 years ago
[Newsletters] Need to localize email confirm & email preference center for: IT, BG, NL, CS
Categories
(www.mozilla.org :: L10N, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jdavis, Assigned: flod, Mentored)
Details
User story:
As a person who has subscribed to email newsletters from the Copyright petition in IT, BG, NL, or CS, I want to be able to confirm my subscription and manage my email preferences in my language. (Right now, it's all in English.)
Example links:
https://www.mozilla.org/en-US/newsletter/existing/2624282a-df82-4893-ab53-1c99f8c9fcae/
https://www.mozilla.org/en-US/newsletter/confirm/2624282a-df82-4893-ab53-1c99f8c9fcae/
These pages are currently supported in:
EN, ES, PT, DE, FR, RU, ID, PL
They need to be localized into:
IT, BG, NL, CS
to support the Foundation's work for their Copyright/Maker Party campaign.
Related (but not blocking this work):
Bug 1297399
Assignee | ||
Comment 1•8 years ago
|
||
This is not exactly a small task to localize (1k words), especially out of the blue when there's a lot of other things going on (home page, pre-release, and the campaign itself). It also means that these 4 locale will get a request to localize content from now on when there's an update for newsletter.
Is the content of the newsletter they receive localized as part of the Campaign?
Reporter | ||
Comment 2•8 years ago
|
||
The timing on this is flexible. The signup experience isn't ideal, but it's okay. It'll work.
The confirmation email itself has already been localized and any new campaign information will be localized as needed separately (the Foundation is working on how to handle ongoing localizations).
If they need to take on the task of getting these words localized, like they did with the campaign information, please let Andrea/Steph know.
Comment 3•8 years ago
|
||
We currently have two new contributors, who are getting familiar with Pontoon and first translations in Aurora right now. My ETA is a week or two if we can use Pontoon or similar tool. But it also depends how much content of the newsletters is there too.
Assignee | ||
Comment 4•8 years ago
|
||
I've already CCed one localizer for each of the languages involved.
In the next days I'll expose the strings, please let me know if you don't think you'll be able to manage this and we'll have the agency work on the file. In the end, those strings need to land as .lang file in the repository, so you'll have the final word on the content.
@Mikk
Content will be exposed in Pontoon. The file is already there for a few locales, not sure if we need to add some strings or not (I'm aware of a pending request)
@Jess
I have no idea if there's anything else that needs to be done on Bedrock's side, besides me exposing those files (not familiar enough with newsletters).
For reference, Peiying is responsible for mozilla.org l10n now, I'm just covering for her while she's on PTO.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → francesco.lodolo
Comment 5•8 years ago
|
||
I find this exiting. Bulgarian is in.
Assignee | ||
Comment 6•8 years ago
|
||
I've just added the file to all locales. The good news is that I was able to import half of the strings from the old newsletter file, so it shouldn't be a long file to localize, despite the number of missing strings.
Updated•8 years ago
|
Summary: Need to localize email confirm & email preference center for: IT, BG, NL, CS → [Newsletters] Need to localize email confirm & email preference center for: IT, BG, NL, CS
Assignee | ||
Comment 7•8 years ago
|
||
At the moment we're only missing a few strings for cs
https://l10n.mozilla-community.org/langchecker/?locale=all&website=0&file=mozorg/newsletters.lang
Comment 8•8 years ago
|
||
Czech is ready now.
Assignee | ||
Comment 9•8 years ago
|
||
Thanks, we can close this one then.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 10•8 years ago
|
||
Wonderful! Thank you all so much! The pages look beautiful :D
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•