Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
do not localize strings in browser/metro
10 views
Skip to first unread message
Axel Hecht
Feb 22, 2013, 5:31:51 PM2/22/13
to
Hi,
please don't spend time on translating strings in browser/metro.
The strings there are not ready for localization, and we're pulling them
from the l10n ecosystem. That's already landed on central, I hope to get
it landed soon on aurora, too.
If you've spent work on those strings, it may be work lost, sadly. The
strings are really not ready, that is, once we switch metro l10n back
on, changed strings may not have changed their key. That is,
compare-locales and the dashboard aren't going to report on them.
There's a thread in .planning on how the communication between the metro
team and us fell down.
Axel
please don't spend time on translating strings in browser/metro.
The strings there are not ready for localization, and we're pulling them
from the l10n ecosystem. That's already landed on central, I hope to get
it landed soon on aurora, too.
If you've spent work on those strings, it may be work lost, sadly. The
strings are really not ready, that is, once we switch metro l10n back
on, changed strings may not have changed their key. That is,
compare-locales and the dashboard aren't going to report on them.
There's a thread in .planning on how the communication between the metro
team and us fell down.
Axel
Axel Hecht
Feb 26, 2013, 5:34:59 AM2/26/13
to
This also landed on aurora now. No more metro strings until we change
that again.
Dashboard should update in a few.
Axel
that again.
Dashboard should update in a few.
Axel
0 new messages