1577027 - Translate Strings in DNS over HTTPS Add-on

Status: RESOLVED FIXED

(Mozilla Localizations :: Other, task)

Description

[Wayne Thayer]

This request is in support of 1573840.

The add-on code is at https://github.com/mozilla/doh-rollout/

Comment 1

[Jeff Beatty [:gueroJeff]]

Thanks for filing this bug, Wayne. Please refer to the Localization page on Mana (https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=66651657) for the correct process to make these requests in bugzilla. I've placed this under the correct Product::Component and removed the assignee (we triage, then assign). Please include the following information to round out this request:

Project owner:
Description of target audience:
Where the source content (will) lives: https://github.com/mozilla/doh-rollout/
Target locales:
Reference materials (e.g., is the standard style guide sufficient? Is there specific terminology needed for this?): 
Project's roadmap (URL preferred):
Project's target release date:

I know some of this was discussed over email, but it truly needs to live in the bug request.

Comment 2

[Wayne Thayer]

Project owner: EPM: Wayne Thayer, PM: Arthur Edelstein
Description of target audience: All desktop users in the US will be targeted with the notification in this add-on
Where the source content (will) lives: https://github.com/mozilla/doh-rollout/
Target locales: Per https://sql.telemetry.mozilla.org/queries/61804#158997 , en, zh, and es are the most important, but we'd like to target this to all users in the US and not be limited by translated locales.
Reference materials (e.g., is the standard style guide sufficient? Is there specific terminology needed for this?):
Project's roadmap (URL preferred): https://docs.google.com/spreadsheets/d/1KateCrxEUrZuuVY1XurT0dCGVb0hg9dKinegVZPCHoA/edit#gid=0
Project's target release date: 24-Sept 2019

Comment 3

[Francesco Lodolo [:flod]]

(In reply to Wayne Thayer [:wayne] from comment #2)

Target locales: Per https://sql.telemetry.mozilla.org/queries/61804#158997 , en, zh, and es are the most important, but we'd like to target this to all users in the US and not be limited by translated locales.

Can you clarify this bit? We're going to target all users in US, and that's clear. What is unclear is if the request is to expose for localization in Pontoon to a list of locales (es-ES, zh-CN), or to all locales.

Given the distribution, we could extend it a bit, but I wouldn't go further down than Russian (there's quite a jump between 9 and 10).

Comment 4

[Francesco Lodolo [:flod]]

Project is enabled in Pontoon, just for zn-CN and es-ES, pending questions in comment 3.
https://pontoon.mozilla.org/projects/dns-over-https-roll-out/

(In reply to Francesco Lodolo [:flod] from comment #3)

Can you clarify this bit? We're going to target all users in US, and that's clear. What is unclear is if the request is to expose for localization in Pontoon to a list of locales (es-ES, zh-CN), or to all locales.

Comment 5

[Wayne Thayer]

(In reply to Francesco Lodolo [:flod] from comment #4)

Project is enabled in Pontoon, just for zn-CN and es-ES, pending questions in comment 3.
https://pontoon.mozilla.org/projects/dns-over-https-roll-out/

(In reply to Francesco Lodolo [:flod] from comment #3)

Can you clarify this bit? We're going to target all users in US, and that's clear. What is unclear is if the request is to expose for localization in Pontoon to a list of locales (es-ES, zh-CN), or to all locales.

From my perspective, the more locales the better, and ideally all locales. I know nothing about how these decisions are typically made and the "cost" of adding more locales, so I'm looking for your guidance on this decision.

Given the distribution, we could extend it a bit, but I wouldn't go further down than Russian (there's quite a jump between 9 and 10).

If you think it makes sense to translate to the top 9 locales, please do so.

Comment 6

[Francesco Lodolo [:flod]]

OK. I'm going to enable the top 9 languages, and see how it goes it the coming days.

There's not much cost in adding more locales. The major risk is diverging attention from high priorities projects, when this add-on has little impact for most languages, and that's something I'd like to avoid.

Comment 7

[Wayne Thayer]

The notification string to be translated has not been finalized yet, so if comment 6 means that translations have been started, please hold off. I'm hoping to get the final signoff today. The proposed language, pending approval, is:

“Firefox will now encrypt and route DNS lookups whenever possible to a trusted partner, unless your device or network uses custom DNS settings. This helps protect against phishing, malware, and surveillance. Learn more”

Comment 8

[Francesco Lodolo [:flod]]

(In reply to Wayne Thayer [:wayne] from comment #7)

The notification string to be translated has not been finalized yet, so if comment 6 means that translations have been started, please hold off. I'm hoping to get the final signoff today. The proposed language, pending approval, is:

“Firefox will now encrypt and route DNS lookups whenever possible to a trusted partner, unless your device or network uses custom DNS settings. This helps protect against phishing, malware, and surveillance. Learn more”

Localization has started, because nobody thought of mentioning that the content wasn't final, in the email thread or in the request.

That's not how these requests should be managed, honestly.

Comment 9

[Francesco Lodolo [:flod]]

I temporarily disabled the project, and will need to reach to Chinese, given they already translated those strings.

Comment 10

[Wayne Thayer]

The copy in comment #8 was just approved and has been communicated to Jonathan for incorporation into the addon.

I don't expect any further changes to strings, but there is still dev work happening on the addon this week.

Comment 11

[Jonathan Kingston [:jkt] he/him]

I merged the latest change into the addon now.

Comment 12

[Francesco Lodolo [:flod]]

(In reply to Jonathan Kingston [:jkt] from comment #11)

I merged the latest change into the addon now.

It needs to be pushed in the branch used by Pontoon to read and write content too.

Comment 13

[Francesco Lodolo [:flod]]

Pushed the commit myself on the branch, will re-enable Pontoon in a few minutes.

Comment 14

[Francesco Lodolo [:flod]]

(In reply to Wayne Thayer [:wayne] from comment #10)

I don't expect any further changes to strings, but there is still dev work happening on the addon this week.

Is there more background on this change?
https://github.com/mozilla/doh-rollout/pull/54

We have almost all locales done, if we invalidate the existing string it brings up back to step 1.

Comment 15

[Wayne Thayer]

That change came out of an exec review of our rollout plans. It is a clarification, so can we use the existing translations until the change can be translated?

Comment 16

[Francesco Lodolo [:flod]]

(In reply to Wayne Thayer [:wayne] from comment #15)

That change came out of an exec review of our rollout plans. It is a clarification, so can we use the existing translations until the change can be translated?

For that, we would need to expose the new string as a separate string, and keep using the old one in the code for every language until the languages we care about are done.

Comment 17

[Wayne Thayer]

The priority is on using the new string for en_US, so treating the new wording as a separate string won't work.

Comment 18

[Francesco Lodolo [:flod]]

I consider this bug done at this point (all enabled locales are at 100%), although I don't know what's the current shipping status of the add-on.

Comment 19

[Maxx Crawford [:maxx]]

Per :wayne, the target launch date is October 15th.