1208291 - Update Email Preference Center with Localized strings for Foundation Newsletters

Status: RESOLVED FIXED

(www.mozilla.org :: L10N, defect)

Description

[Jessilyn Davis]

The Foundation is moving into our email preference center! \o/

The EN versions are currently live. We need help localizing and implementing the new newsletter names and descriptions in our email newsletter languages:

DE, FR, PT(-BR), ES (general), PL, ID, RU

Here are the new newsletters and their descriptions:

Mozilla Foundation
News and special updates about our work to promote openness, innovation and participation on the Internet, including ways for you to get involved.


Webmaker
Special announcements helping you get the most out of Webmaker.


Mozilla Learning Network
Updates from our global community, helping people learn the most important skills of our age: the ability to read, write and participate in the digital world.


Mozilla Festival
Special announcements about Mozilla's annual, hands-on festival dedicated to forging the future of the open Web.


Maker Party
Mozilla's largest celebration of making and learning on the web.


Timing: Q4, sooner rather than later, but should not block other work (ie Bug 1199799 is the current priority, and we can potentially wait until Bug 1197244 is implemented if it looks doable in the coming weeks).

Please let me know your questions.

Thanks!

Comment 1

[Pascal Chevrel:pascalc]

We really need all those strings to be back in a template on Bedrock if you want to scale up the newsletter center, there is no bug opened for that but I talked with pmac recently about it on IRC. CCing him to know his thoughts.

pmac, could we get the strings in the newsletter center in Q4?

Comment 2

[Paul [:pmac] McLanahan]

(In reply to Pascal Chevrel:pascalc from comment #1)
> We really need all those strings to be back in a template on Bedrock if you
> want to scale up the newsletter center, there is no bug opened for that but
> I talked with pmac recently about it on IRC. CCing him to know his thoughts.
> 
> pmac, could we get the strings in the newsletter center in Q4?

I'd say definitely. Shouldn't be difficult to do, just need to get it in the queue.

Comment 3

[Jessilyn Davis]

Sounds like a plan. Thank you both!

Comment 4

[Adam Lofting (:adamlofting)]

This might be a stupid question, but is it possible to include/exclude certain lists by certain locales? For example, I can't see us having the resources to communicate with the Mozfest list in non-en languages. 

If not, it's not the end of the world if people opt-in to silent channels, but it might be a little bit of a let down for them. 

If this would be a new feature and it adds significant complexity, the benefit might not justify the effort.

Comment 5

[Jessilyn Davis]

(In reply to Adam Lofting (:adamlofting) from comment #4)
> This might be a stupid question, but is it possible to include/exclude
> certain lists by certain locales? For example, I can't see us having the
> resources to communicate with the Mozfest list in non-en languages. 

Not a stupid question and something I've been struggling with trying to solve myself! When we only had a 1 or 2 other "English Only" newsletters, it made sense; but as we've expanded, and may continue to expand, it's important to keep the Email Preference Center clear and easy to navigate for the user. I've been thinking about how to address + tackle this for Q4 this year. 

Your proposal is an interesting idea.


Pmac, Pascal - what do you think about the ability to turn on/off: 1) certain strings to be l10ned, 2) certain newsletters to show/not show for non-EN locales? (Unless they are subscribed to the newsletter, then it should show, but it would be ok for it to be in English since the email stream is EN only.)

Comment 6

[Pascal Chevrel:pascalc]

Is there something(In reply to Jessilyn Davis from comment #5)
> 
> Pmac, Pascal - what do you think about the ability to turn on/off: 1)
> certain strings to be l10ned, 2) certain newsletters to show/not show for
> non-EN locales? (Unless they are subscribed to the newsletter, then it
> should show, but it would be ok for it to be in English since the email
> stream is EN only.)

We can have strings non-localizable and displayed in English, we can also have strings that appear only on a specific locale, in that case English.

About preventing non English speakers from subscibing to newsletters in English, personally I  don't agree, it's not because I am not a native English speaker that I don't speak English enough to subscribe to a newsletter in this language. Similarily, we don't hide our Firefox download links to users for which we don't have a localized build, we let them download the English build.

Comment 7

[Jessilyn Davis]

+1 Great point, Pascal.  Let's carry on with showing all the newsletters to all the languages. 

Do you have a recommendation on how to handle if we should localize the Newsletter Title & Description for newsletters that are English only? Is it a better experience to have the information only in English? Or localized with a "(English only)" (that's also localized) beside it?

Comment 8

[Pascal Chevrel:pascalc]

so FYI, all the strings requested were added a few days ago to the new mozorg/newsletters.lang file and are being translated by the locales that do translate our newsletter:
https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=0&file=mozorg/newsletters.lang

On the l10n side, there isn't much more than we can do as we don't work on the basket side of things, so when the above dashboard shows that all locales have translated it, this bug can be closed.

Comment 9

[Pascal Chevrel:pascalc]

(In reply to Jessilyn Davis from comment #7)
> +1 Great point, Pascal.  Let's carry on with showing all the newsletters to
> all the languages. 
> 
> Do you have a recommendation on how to handle if we should localize the
> Newsletter Title & Description for newsletters that are English only? Is it
> a better experience to have the information only in English? Or localized
> with a "(English only)" (that's also localized) beside it?

For now we translate everything that is in the Json api on basket, keeping some titles in English is an option we can consider, but this is manageable only if this is in a proper template so we should discuss it in Bug 1210396

Comment 10

[Francesco Lodolo [:flod]]

Assuming this is fixed by now.