1001220 - [l10n][2.0] Merge test locales in Github for developers

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia, defect)

Description

[Théo Chevalier]

It's been a while since we merged those locales, let's do that again, even if Firefox OS 2.0 l10n has not started yet (will happen in a few days, though).

Comment 1

[Ahmed Nefzaoui [:Nefzaoui]]

(In reply to Théo Chevalier [:tchevalier] from comment #0)
> It's been a while since we merged those locales, let's do that again, even
> if Firefox OS 2.0 l10n has not started yet 

Thanks, this definitely helps. :)

>(will happen in a few days, though).

Is there a "Firefox OS l10n schedule" somewhere that I should keep an eye at when working on localization?

Thanks

Comment 2

[Théo Chevalier]

(In reply to Ahmed Nefzaoui [:Nefzaoui] from comment #1)
> (In reply to Théo Chevalier [:tchevalier] from comment #0)
> > It's been a while since we merged those locales, let's do that again, even
> > if Firefox OS 2.0 l10n has not started yet 
> 
> Thanks, this definitely helps. :)

Thanks to you and the team for the translation update! If you want me to merge it again, do not hesitate to open a bug and CC me ;)

> 
> >(will happen in a few days, though).
> 
> Is there a "Firefox OS l10n schedule" somewhere that I should keep an eye at
> when working on localization?
> 
> Thanks

We don't have anything final at the moment, still working on it. But if everything goes well, we should be able to start localizing master next week.
Monday is hard string freeze for 1.4

Comment 3

[Peter Pin-Guang Chen [:petercpg] (MozTW.org)]

Théo, is there anything to do for zh-TW at my side? Our progress for gaia-l10n have been green for some time and should be able to catch up in short time when new strings are imported.

Thanks :)

Comment 4

[Théo Chevalier]

(In reply to Peter Pin-Guang Chen [:petercpg] (MozTW.org) from comment #3)
> Théo, is there anything to do for zh-TW at my side? Our progress for
> gaia-l10n have been green for some time and should be able to catch up in
> short time when new strings are imported.
> 
> Thanks :)

Hey Peter, you don't have anything to do in particular, just keep up the good work, and maybe ping me (or file a bug) once 2.0 l10n is done for zh-TW so that I can merge again

Comment 5

[Théo Chevalier]

Attachment: Link to Github PR

Comment 6

[Théo Chevalier]

Tim, maybe for PR containing only strings like this one, I could ask Stas or Gandalf for review?

Comment 7

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Comment on attachment 8413253 [details] [review]
Link to Github PR

I can rubber-stamp this.

Noted that after bug 968666 and bug 900182, I intend to remove these locale strings from Gaia tree; we will programmatically generate fake locales (e.g. Accented English zz-ZZ) when build Gaia instead.

Comment 8

[Théo Chevalier]

(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from comment #7)
> Comment on attachment 8413253 [details] [review]
> Link to Github PR
> 
> I can rubber-stamp this.

Thanks
> 
> Noted that after bug 968666 and bug 900182, I intend to remove these locale
> strings from Gaia tree; we will programmatically generate fake locales (e.g.
> Accented English zz-ZZ) when build Gaia instead.

Sure, that was the plan

Comment 9

[Ahmed Nefzaoui [:Nefzaoui]]

(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from comment #7)
> Comment on attachment 8413253 [details] [review]
> Link to Github PR


> Noted that after bug 968666 and bug 900182, I intend to remove these locale
> strings from Gaia tree; we will programmatically generate fake locales (e.g.
> Accented English zz-ZZ) when build Gaia instead.

Let's not forget that Arabic (among others) use a different Font (Droid Arabic Naskh, Bug #893530) which means detecting style issues for Arabic will be harder (I'm filing one right now btw) for localizers if they don't have Arabic itself in their daily FOTAs, not to mention that not all localizers are technical enough to understand how to get a locale, merge it into gaia's and build it into their devices.

Comment 10

[Ryan VanderMeulen [:RyanVM]]

Master: https://github.com/mozilla-b2g/gaia/commit/f50d8a3504e0a57d371457c50a6ced333e20724d

Comment 11

[Tim Guan-tin Chien [:timdream] (please needinfo)]

(In reply to Ahmed Nefzaoui [:Nefzaoui] from comment #9)
> Let's not forget that Arabic (among others) use a different Font (Droid
> Arabic Naskh, Bug #893530) which means detecting style issues for Arabic
> will be harder (I'm filing one right now btw) for localizers if they don't
> have Arabic itself in their daily FOTAs, not to mention that not all
> localizers are technical enough to understand how to get a locale, merge it
> into gaia's and build it into their devices.

Let's move to bug 900182 to discuss what we need. I was thinking about

* Accented English
* Fake Long English (every string repeats itself twice)
* Fake RTL English (keeping strings in English while switching to RTL layout)

We certainly need your expertise to tell whether or not these fits our use cases.