Updates on l10n.mozilla.org

[Axel Hecht]

Hi,

we just deployed a new feature on elmo, and one thing you might be
interested in.

If you're working on l10n under more than one locale code, we can now
show all those codes on your team page. The non-primary locale codes
don't get listed on the /teams/ page anymore, and trying to get to their
individual team page redirects to the primary one.

I expect to switch that on for

ja, ja-JP-mac
sr, sr-Cyrl, sr-Latn
hi-IN, hi
gu-IN, gu
pa-IN, pa

I don't expect to do this for 'es'.

Not sure about nb-NO and nn-NO. That would essentially remove one from
the list of localizations, which sounds bad. We could potentially use
'no' as locale code, and gather both nb and nn on that.

Are there other opportunities that I missed. Any of the Indian locales
up there prefer to have the primary locale be the non -IN one?

So much for the team stuff.

Technical detail, I've added CORS headers to the status json that the
exhibit tables use. So you can now write your own status reporter.
Please be patient with the use, this is not the cheapest data to get,
and you're working on a shared resource we all rely on.

Axel

[Aman Alam]

On ਮੰਗਲਵਾਰ 01 ਅਕਤੂਬਰ 2013 10:43 ਸਵੇਰੇ, Axel Hecht wrote:
> Hi,
>
> we just deployed a new feature on elmo, and one thing you might be
> interested in.
>
> If you're working on l10n under more than one locale code, we can now
> show all those codes on your team page. The non-primary locale codes
> don't get listed on the /teams/ page anymore, and trying to get to their
> individual team page redirects to the primary one.
>
> I expect to switch that on for
>
> ja, ja-JP-mac
> sr, sr-Cyrl, sr-Latn
> hi-IN, hi
> gu-IN, gu
> pa-IN, pa

thanks Axel for changes.


--
A S Alam