L10N In Support Of FF37 What's new

RESOLVED FIXED

Status

www.mozilla.org
L10N
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: bensternthal, Assigned: pascalc)

Tracking

Production
x86
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

User Story

de
es-ES
es-MX
fr
id
pt-BR

Attachments

(2 attachments)

(Reporter)

Description

3 years ago
== Wiki ==
https://wiki.mozilla.org/Websites/Mozilla.org/FFReleases/37

== Schedule ==
https://docs.google.com/a/mozilla.com/spreadsheets/d/1K17Po97qj3vV2BsB6CwWNLFBWYOxoQVYRD-XDWikIvY/edit?usp=sharing

Strings Ready For l10n: 2015-03-13
Launch Date: 2015-03-30

See user story whiteboard for locale list.
(Assignee)

Updated

3 years ago
Assignee: nobody → pascalc
(Assignee)

Updated

3 years ago
User Story: (updated)
Quick question - if we're only localizing a small subset of locales for this whatsnew page, is this page being triggered in-product for only these locales above? If not, what should every other locale see?
Flags: needinfo?(bsternthal)
(Assignee)

Comment 2

3 years ago
I think release engineering can activate the What's New page for the set of locales we want and other locales wouldn't have a What's New page, pinging Sylvestre to know if this is possible.
Flags: needinfo?(sledru)
Ben can probably answer to that question. We, release manager, don't manage the What's new page.
Flags: needinfo?(sledru) → needinfo?(bhearsum)
(In reply to Pascal Chevrel:pascalc from comment #2)
> I think release engineering can activate the What's New page for the set of
> locales we want and other locales wouldn't have a What's New page, pinging
> Sylvestre to know if this is possible.

Yeah, we can do this. We need to know the address of the whatsnew page and the locales that should have it *before* we build the release, though.
Flags: needinfo?(bhearsum)
(Reporter)

Comment 5

3 years ago
Sorry for the delay responding I was out sick yesterday.

We are targeting geo-graphical locations with this version of FF What's New. So the following is how this will work.

1. Whats New Turned On For All Users For FF37 Bug was filed a while ago See -> https://bugzilla.mozilla.org/show_bug.cgi?id=1134471
2. Web Site uses GeoDude (pmac advised here) to display this page to correction geo-graphical locations.
3. For folks not included in the Geo list, they are shown a (I still need to sort the details out here) one of our existing what's new pages. Although winston said he preferred if they were just shown the tab page.. but Im not sure if thats possible.
Flags: needinfo?(bsternthal)
(In reply to Ben (:bensternthal) from comment #5)
> 3. For folks not included in the Geo list, they are shown a (I still need to
> sort the details out here) one of our existing what's new pages. Although
> winston said he preferred if they were just shown the tab page.. but Im not
> sure if thats possible.

Geo-location !== page locale.

Where a user is located in the world has no bearing to the language they have their browser set to. This will require us to translate this page for every locale, not just the list above.

We can either translate for all locales, or show this new page to only the subset above.
Working branch is: https://github.com/mozilla/bedrock/tree/bug-1134414-ff37-whatsnew-page

Template can be found at: https://github.com/mozilla/bedrock/blob/bug-1134414-ff37-whatsnew-page/bedrock/firefox/templates/firefox/whatsnew-fx37.html

This should contain the up-to-date strings in the copy doc found in Bug 1134401.

I'm still waiting on getting a demo server for this branch, but should hopefully have one soon and will update here.
(Assignee)

Comment 8

3 years ago
(In reply to Ben (:bensternthal) from comment #5)
> Sorry for the delay responding I was out sick yesterday.
> 
> We are targeting geo-graphical locations with this version of FF What's New.
> So the following is how this will work.
> 
> 1. Whats New Turned On For All Users For FF37 Bug was filed a while ago See
> -> https://bugzilla.mozilla.org/show_bug.cgi?id=1134471

This changes the scope of this project greatly, it's no longer a handful of locales we need but all of the locales supported by Firefox.
(Reporter)

Comment 9

3 years ago
Pascal - we are working on a solution so that is not all locations but still the list we sent you originally. Once I have it all sorted I will update the bug.
Ok this is now up on a demo server:

https://www-demo3.allizom.org/en-US/firefox/37.0/whatsnew/

To the best of my knowledge all strings from Bug 1134401 are considered final, and should be in the template above for l10n.

Please note: this is just a basic template at the minute. The SMS form does not yet have plumbing, the email form just points to our regular newsletter still. The geo-location work has also yet to be implemented.
Ok looks like we are not quite yet string frozen - there may be one final addition we are waiting on: https://bugzilla.mozilla.org/show_bug.cgi?id=1134414#c6

Think we should be good to call string freeze on Friday - either Ben or myself will comment when we officially have the green light.
Another note:

When someone enters the sms number incorrectly, the server returns an error message like:

"Sorry. This number isn't valid. Please enter a U.S. phone number or<a href="http://mzl.la/OgZo6k">download directly from Google Play.</a>"

I asked pmac and he says bedrock returns a localized string here, so we don't need to include these in the template. But we should still make sure these error messages are translated in the languages we need.
(Assignee)

Comment 13

3 years ago
(In reply to Alex Gibson [:agibson] from comment #12)
> Another note:
> 
> When someone enters the sms number incorrectly, the server returns an error
> message like:
> 
> "Sorry. This number isn't valid. Please enter a U.S. phone number or<a
> href="http://mzl.la/OgZo6k">download directly from Google Play.</a>"
> 
> I asked pmac and he says bedrock returns a localized string here, so we
> don't need to include these in the template. But we should still make sure
> these error messages are translated in the languages we need.

Thanks Alex, I'll make sure to include this string in the lang file.
Ok we are good to call for string freeze, as per: https://bugzilla.mozilla.org/show_bug.cgi?id=1134401#c29
(Assignee)

Comment 15

3 years ago
Strings sent to localizers, mini dashboard for this page: https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=0&file=firefox/whatsnew-fx37.lang

Please note that we will translate German last as we will be using this page to test new volunteers in this language.
Geo-location is now in place on demo3, so only people in the US will be able to see the SMS form.

To help localizers outside of the US to test their changes, I've added a simple query param to enable showing the SMS form:

https://www-demo3.allizom.org/en-US/firefox/37.0/whatsnew/?geo=us
(Assignee)

Comment 17

3 years ago
(In reply to Alex Gibson [:agibson] from comment #16)
> Geo-location is now in place on demo3, so only people in the US will be able
> to see the SMS form.
> 
> To help localizers outside of the US to test their changes, I've added a
> simple query param to enable showing the SMS form:
> 
> https://www-demo3.allizom.org/en-US/firefox/37.0/whatsnew/?geo=us

Great, thanks Alex! :)
Pascal, I'm still seeing the SMS error message in Comment 12 untranslated, e.g:

https://www-demo3.allizom.org/id/firefox/37.0/whatsnew/?geo=us

Maybe this string is just not yet completed, but I just want to make sure it doesn't slip through the cracks.
(Assignee)

Comment 19

3 years ago
(In reply to Alex Gibson [:agibson] from comment #18)
> Pascal, I'm still seeing the SMS error message in Comment 12 untranslated,
> e.g:
> 
> https://www-demo3.allizom.org/id/firefox/37.0/whatsnew/?geo=us
> 
> Maybe this string is just not yet completed, but I just want to make sure it
> doesn't slip through the cracks.

The string is translated and in the lang file, it may be that the python file needing the string expects the string from one of the global UI files (main.lang, newsletter.lang) but I wouldn't want to add this string for translation to all locales while we are using it for just a subset of locales. Let me check locally.
(Assignee)

Comment 20

3 years ago
Created attachment 8579330 [details] [diff] [review]
form.diff

Alex, here is a patch adding the line needed in the python file to load the translations from the lang file (I can do a PR if needed)
(In reply to Pascal Chevrel:pascalc from comment #20)
> Created attachment 8579330 [details] [diff] [review]
> form.diff
> 
> Alex, here is a patch adding the line needed in the python file to load the
> translations from the lang file (I can do a PR if needed)

Many thanks Pascal, I should be able to see to adding this ok
Created attachment 8579338 [details]
sms-error-message.png

Seeing the correct translated string now :)
Note: I've updated the PR to include strings for the og meta content, which we're recently added to main.lang in Bug 1140186.
(Assignee)

Comment 24

3 years ago
(In reply to Pascal Chevrel:pascalc from comment #15)
> Strings sent to localizers, mini dashboard for this page:
> https://l10n.mozilla-community.org/~pascalc/langchecker/
> ?locale=all&website=0&file=firefox/whatsnew-fx37.lang
> 
> Please note that we will translate German last as we will be using this page
> to test new volunteers in this language.

All locales are translated, en-GB uses en-US strings as we recently added en-GB as a real locale on mozilla.org but don't have yet British localizers to actually fix spelling/reword strings currentlty in American English.

Marking fixed.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.