860969 - Mozillians Homepage: L10N Review

Status: RESOLVED INVALID

(Participation Infrastructure :: Phonebook, defect)

Description

[Justin Crawford [:hoosteeno] [:jcrawford]]

In Q2 we have a goal that includes deploying a redesigned homepage (for logged out and logged in states). This will mean at least a few new strings will need to be reviewed and translated. The strings don't exist yet; this bug is intended as a heads-up. I will update the bug when there are strings (the blocking bug 860956 describes that effort).

In addition to a normal review, we want to be very sure that the design anticipates R-to-L text.

Comment 1

[Justin Crawford [:hoosteeno] [:jcrawford]]

The strings have been created and reviewed; these are as close to final as they can be before code:

https://mozillians.etherpad.mozilla.org/homepage-redesign-strings

The code will be landing on mozillians-dev.allizom.com in the next few weeks.

Comment 2

[Pascal Chevrel:pascalc (PTO until April 26)]

CCing a couple of people from l10n-drivers as I will be on holidays on Tuesday

Comment 3

[Francesco Lodolo [:flod]]

Design looks good, my only concern is the search fields' widths: the localized version of "Search by name or group" or "Search for people, groups and more" could be a much longer string, and it needs to be displayed entirely to make sense.

Comment 4

[Justin Crawford [:hoosteeno] [:jcrawford]]

:flod, we've made the search fields bigger, thanks for your comment!

In other news, new strings are now live on dev:

https://mozillians-dev.allizom.org/en-US/

We intend to launch this new site on 6/27. Please reach out with any questions.

Comment 5

[Francesco Lodolo [:flod]]

Do you already have an estimate of the number of changed strings? Localizers will probably need at least a couple of weeks for localizing and testing, so the sooner we have these strings the better.

Comment 6

[Justin Crawford [:hoosteeno] [:jcrawford]]

The link in comment 1 (https://mozillians.etherpad.mozilla.org/homepage-redesign-strings) is still the best source for information about the specific strings that we've added. Right now it looks like about 10 new strings.

Comment 7

[Justin Crawford [:hoosteeno] [:jcrawford]]

We're still planning to launch the new homepage in Q2. A more detailed launch plan can be found in this thread: https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.community-tools/jw8uBe95dPY

In summary, we'll push the major homepage changes to staging (mozilla.allizom.org) on 6/13 in preparation for a launch on/around 6/27. 

Please let me know if I can provide additional information to facilitate L10N. Thanks!

Comment 8

[Francesco Lodolo [:flod]]

(In reply to Justin Crawford [:hoosteeno] from comment #7)
> In summary, we'll push the major homepage changes to staging
> (mozilla.allizom.org) on 6/13 in preparation for a launch on/around 6/27. 

And the strings will be ready for translation on? Let's just hope we don't hit some major problems with localizability ;-)

Comment 9

[Justin Crawford [:hoosteeno] [:jcrawford]]

The strings are "ready" for translation now. But we don't know how to make them available to you without clobbering strings on the current, live site. Can you please advise how best to give l10n team access to the new strings?

An example:
* The current, live site has a string in the footer, "Other Languages". This string is translated. But the new site does not have this string.
* The new site has a string, "Search for people, groups and more". This string is not yet translated, because it's never been committed to SVN.
* If we commit the result of a string extract/merge from the new site, the new string will be available for translation, and the old string will simply disappear. 
* That means the current live site will no longer get translations for "Other Languages".

Ideas:
1) We could manually modify messages.po in every locale to prevent current valid strings from being deleted
2) We could create a fake template that contains a superset of current and new strings, all of which would be included in messages.po, so everything would be available for translation
3) We could wait until the site is launched before committing strings for translation
4) ???

Thanks for your help.

Comment 10

[Francesco Lodolo [:flod]]

(In reply to Justin Crawford [:hoosteeno] from comment #9)
> The strings are "ready" for translation now. But we don't know how to make
> them available to you without clobbering strings on the current, live site.
> Can you please advise how best to give l10n team access to the new strings?

Let's see if Pascal has more ideas, considering he has much more experience on the "management part" of these project.

> An example:
> * The current, live site has a string in the footer, "Other Languages". This
> string is translated. But the new site does not have this string.
> * The new site has a string, "Search for people, groups and more". This
> string is not yet translated, because it's never been committed to SVN.
> * If we commit the result of a string extract/merge from the new site, the
> new string will be available for translation, and the old string will simply
> disappear. 

Not sure how the current structure is, but I guess mozillians has at least production and dev (https://mozillians-dev.allizom.org/it/). 

If production doesn't take strings directly from SVN but has a local checkout, why not just update strings on SVN and stop doing checkouts from prod until the new design is published?

> 3) We could wait until the site is launched before committing strings for
> translation

This shouldn't even be an option ;-)

Comment 11

[Justin Crawford [:hoosteeno] [:jcrawford]]

> 
> If production doesn't take strings directly from SVN but has a local
> checkout, why not just update strings on SVN and stop doing checkouts from
> prod until the new design is published?

We control the update script, and it does update the locale directory:

https://github.com/mozilla/mozillians/blob/master/bin/update_site.py#L56

We need confirmation that this is the only way strings are updated on prod. If so, we're in the clear; we'll just avoid pulling new strings until the new code is launched.

Comment 12

[Andrei Hajdukewycz [:sancus]]

I've performed a string merge in r117043, and sent an email to Milos requesting an update of verbatim.

We won't push prod until the homepage redesign is ready, so strings there shouldn't update until that time.

Comment 13

[Francesco Lodolo [:flod]]

On a side note: you added a string with plural form, so you need to add a "Plural-Forms:" to the header. I didn't find one in my locale (r117060). Not sure if Verbatim will add it.

Comment 14

[Milos Dinic [:Milos]]

Verbatim updated, 103 new strings merged in.

Comment 15

[Francesco Lodolo [:flod]]

(In reply to Francesco Lodolo [:flod] from comment #13)
> On a side note: you added a string with plural form, so you need to add a
> "Plural-Forms:" to the header.

To clarify, it seems that only 4 locales has this issue:  eo, hu, id, it.

Comment 16

[Nikos Roussos [:comzeradd]]

Pascal this probably needs your input.

Comment 17

[Francesco Lodolo [:flod]]

Input on what exactly? This bug seems fixed a long time ago, if we still need to fix something on Verbatim the point of contact would be :mathjaz

Comment 18

[Pascal Chevrel:pascalc (PTO until April 26)]

I am removing the needinfo on me since there isn't a specific question I can answer.

Comment 19

[Greg Cox [:gcox]]

This is work specific to mozillians, which is decom'ed.
If this is found to pertain to people.mozilla.org then please open a new issue.