1135302 - [marketing][masterfirefoxos]: site migration verification and localization needed

Status: RESOLVED WONTFIX

(Mozilla Localizations :: Other, defect)

Description

[Peiying Mo [:CocoMo]]

Please comment in the bug when this request is completed for your locale.  

Hello Localizers,

This project impacts only a few locales. You can ignore this message if yours is not listed below

LOCALES:
Version 1.1: cs, de, el, es, hr, hu, it, pl, pt-BR, sr
Version 1.3T: hi, ta
Version 1.4: bn-BD

REVIEW Environment:
https://prod.masterfirefoxos.com/xx/#-#/; change xx with locale name and #-# with version number in the URL.  For instance Tamil should be https://prod.masterfirefoxos.com/ta/1-3T/

ACTION:
There are three things you need to do:
- Minor localization of navigation strings.  These are added due to site migration and new design. 
- Review existing content localized on the old site.  Verify that the pairing of the English and target language are still intact.
- Videos are in the correct language and topic. 

DEADLINE:
=========
- The new site will turn on on February 25th.  When you go to masterfirefoxos.mozilla.org, you will see the new layout.  Should you miss the deadline please work on it as soon as possible. The update will be pushed out daily automatically or can be done manually when necessary.

SOURCE FILE locations: 
=====================
Access through either Pontoon or Github to make changes and localize a handful of new strings
1). Github: https://github.com/mozilla/masterfirefoxos-l10n/blob/master/xx/LC_MESSAGES/django.po (replace xx with your locale code)
2). Pontoon: https://pontoon.mozilla.org/xx/master-firefox-os/ - replacing xx with your locale

    *New strings* are at the bottom of the list.  Scroll down and you will see them
    *Existing strings*: IMPORTANT: 
        *Version*: To find the strings relevant to your locale/version, use the gray text on the top right side for clue. For example, Serbian and in 1.1 only, you only need to review strings that contain Page path: /1-0/ in light gray color
        *Tags*: If there are any styling related tags, such as <h2>, </h2>... be sure to keep the tags in the target language.
        *Strange looking numbers* or random combo of letter/numbers: ignore these.  They are codes for videos.  Simply do a Copy, so the % of completion is more reflective of what you have done. 
        *URLs* - make sure knowledgebase url is pointing to the corresponding SUMO page if it exists for your language; legal docs links should all exist for your language
        *Making changes*: after each string update, click on SAVE.  


CODE PUSH and REFRESH
=====================
Pontoon will be refreshed once an hour if not sooner. Github should be once a day autocratically. Manual push can be done if necessary.

Comment 1

[Francesco Lodolo [:flod]]

(In reply to Peiying Mo [:CocoMo] from comment #0)
> Please comment in the bug when this request is completed for your locale.  

This bug has not much visibility to localizers. Maybe we should have individual bugs for each localization, and use this one for tracking purposes.

>     *New strings* are at the bottom of the list.  Scroll down and you will
> see them

You can also filter them: left column, click on the funnel icon, select the type of strings you want to see.

Comment 2

[Michael Köhler [:Coce]]

The newsgroup indicates that we still cannot start localizing (the project is disabled on Pontoon), so I hope the deadline is pushed out further. And if we could finally have a clear line instead of chaos, that would be quite helpful for my motivation.

Comment 3

[Matjaz Horvat [:mathjazz]]

I couldn't agree more with Michael - the Master Firefox OS l10n process is a mess and we should take a step back, make sure we are entirely ready and than proceed. PO files are not even in sync with POT, fuzzy strings are mostly useless, wrong locales are enabled in Pontoon etc.

The l10n deadline should be postponed.

Comment 4

[Inma Barrios]

Hi,

'es' needs a thorough revision, and the copy does not keep Firefox OS terminology and voice consistent with other Firefox OS web pages, such as https://www.mozilla.org/es-ES/firefox/os/.

Comment 5

[Peiying Mo [:CocoMo]]

Thank you for all of your feedback and your patience.  I am pushing to delay the launch or at least the localized version.  

Michael, there are two deadlines for you, one for the old site (1.1) migration, and one for the new 2.0 launch.  The latter can be enabled as soon as it is ready.  From what I understand the old site to new is a switch of all or none.  

Inma, the current "old" version is 1.1.  I will open a bug soon for you to work on 2.0. Let's focus on getting the 2.0 version in sync with the latest terminology.

Comment 6

[Peiying Mo [:CocoMo]]

Updating the bug with new info: 

REVIEW Environment:
https://l10n.masterfirefoxos.com/xx/#-#/ ; change xx with locale name and #-# with version number in the URL.  For instance Tamil should be https://l10n.masterfirefoxos.com/ta/1-3T/

ACTION:
There are three things you need to do:
- Minor localization of navigation strings.  These are added due to site migration and new design.  You can find them at the end of the file. 
- Review existing content localized on the old site.  Verify that the pairing of the English and target language are still intact.
- Videos are in the correct language and topics. 

DEADLINE:
- There is no deadline masterfirefoxos.mozilla.org, As soon as you sign off on it, it will be turned on one by one per locale request.

SOURCE FILE locations: Verbatim: https://localize.mozilla.org/projects/masterfirefoxos/
IMPORTANT:
- DO NOT Update the Template
- DO click on the Commit to VCS link so the code is pushed to github

CODE PUSH and REFRESH
Push on github is manual at this point.  Team is working on getting this automated at some point.

Comment 7

[Peiying Mo [:CocoMo]]

+ adding contributors to the bug. If you are not the working on this for your locale, please replace the one who is.

Comment 8

[Michael Köhler [:Coce]]

There are no new strings visible for German but there were on Saturday and they have been translated. Were these all that are required?

Comment 9

[Inma Barrios]

Hi,

Reviewed and updates the Spanish copy, and committed to Github*. Changes are not still visible in the review environment, though.

*https://github.com/mozilla/masterfirefoxos-l10n/commit/06badd39152e3734ea13c2f9fdec152b4a66e0d1

Comment 10

[Peiying Mo [:CocoMo]]

Michael, this should be it, I was promised.  

Inma, the changes may not be immediately pushed from github to test server, this is still a manual process at the moment.  The guy in charge of the push lives in the Southeast of the US.  He will do the pushes during his day time.  We are looking at changing this soon.  

Thanks for the quick update.

Comment 11

[Marcelo Araldi]

Adding Marco Aurélio "Ouesten" to this bug. He is our main translator on Verbatim and is helping with this project.

Comment 12

[Peiying Mo [:CocoMo]]

Hello Inma and everyone, 

In order to see the changes you made in Verbatim reflected on the staging server https://l10n.masterfirefoxos.com/xx/#-#/, you need to make sure to click on the "Commit to VCS" in Verbatim.  If you do not take this step, the changes won't be pushed to the staging server. The push is right away.   DO NOT forget to do it!!

Comment 13

[Peiying Mo [:CocoMo]]

Attachment: Verbatim-commit.png

See the screenshot

Comment 14

[Inma Barrios]

Hi Peiying,

I didn't localize the web page using Verbatim this time. I updated the strings and sent a pull request on Github. Please let me know if you have any questions or concerns.

Comment 15

[Iosif Psychas [:TheGallery]]

Greek is almost done, I've got a question. Should I update the old strings as well? Because I noticed some translations don't match the English strings (maybe they were updated at some point? Someone else did the original translation). 

On a side note, there is a typo in an English string in the top of the page (under the Welcome! header). The last sentence writes "Select any topic top get started." it should obviously write "Select any topic to get started."

Comment 16

[Peiying Mo [:CocoMo]]

Hello Iosif, please do review everything and update, revise if necessary.  The translation was done by someone else more than a year ago, and it was in the form of a Word file.  As described in the original bug, several other factors came to play that made this review a must-do.  Please go over the strings and let me know when you are done.

Thank you for pointing out the typo.  We will get it fixed.

Comment 17

[Francesco Lodolo [:flod]]

Italian is good to go, thanks to Sara for doing most of the revision work.

Comment 18

[Peiying Mo [:CocoMo]]

Thank you Flod.  

Ben, please go ahead to push Italian 1.1 to production.

Comment 19

[Iosif Psychas [:TheGallery]]

Greek have been updated and committed through Verbatim. Sorry for the delay.

Comment 20

[Peiying Mo [:CocoMo]]

Iosif, thank you for the confirmation. Yay!!

Comment 21

[Peiying Mo [:CocoMo]]

pt-BR is complete.

Comment 22

[Michal Stanke (Mozilla.cz) [:mstanke][:MikkCZ]]

Sorry it took us so long. :( Czech (cs) is now 100% too.

Comment 23

[Peiying Mo [:CocoMo]]

Thank you Michal.  Better late than never.  I have filed 1213911 for production push.

Comment 24

[Peiying Mo [:CocoMo]]

The site is in maintenance mode.