Discussion:
Firefox for Android localization update
(too old to reply)
Axel Hecht
2012-09-21 14:57:52 UTC
Permalink
Hi,

here an update on how we plan to move forward with localizing Firefox
for Android, aka, Fennec. This is the outcome of digesting a ton of
ideas, and a call among Karen, Mark, Brad, Alex, Chris, and I.

The goal is to have a snappy product in a good number of languages by
Firefox 19.

"Snappy" comes with two constraints, startup time and download size.

Download size increases significantly with many localizations added, so
we'll work on reducing that impact. That work is tracked in [1], and is
engineered by the mobile team, with help from build peers, hopefully.

The other half of snappy is startup time, and that means that we can't
afford to have a locale selection independent of the Android settings.
Doing so apparently tears down much of the pre-created android process
and sets it up again, noticably slowing down startup.

That means that the list of locales that we're able to put into the
multi-locale build is limited by what Android supports. This is a
strange feeling for us, but we're going after the users that are on
Android, so that's OK.

The future of the single-locale builds isn't yet determined, but as long
as google play store doesn't support an APK per language, they'll not
prominently exposed. Using them on Nightly or Aurora is fine, though.

Practically, I'll work on separating the localizations that we're
shipping as Firefox from those we're not able to ship (yet) on the
dashboard. There will be one list of languages that go into the
multi-locale build, and that will be offered to sign-off etc, and there
will be the remaining list who'll continue to see builds on aurora and
nightly. This won't affect our builds really, it's just clarifying that
on the l10n dashboard.

Data which locales fall into which bucket are in [2].

We'll test extensively what we can achieve in both size and performance,
and then try to add a healthy amount of localizations to Firefox on Android.

Thanks for your support and patience, and sorry if the experience we can
create on Android in your language doesn't work out the way we all hoped.

Axel

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=792077
[2]
https://groups.google.com/forum/#!topic/mozilla.dev.platforms.mobile/gAmPESDpfQc
Armen Zambrano G.
2012-09-21 15:47:57 UTC
Permalink
Thanks for the clarification and it is understandable.

Can we have in-product selection of a language?

I think it could work like this
* select language
* download whatever strings are needed for that specific locale (not
sure if we have something like a langpack for Android)
** I assume we would fall back on English strings if needed

I assume that people who select a language different than their OS'
would be updated to en-US/multilocale and then immediately after
start-up be retrieving the latest set of string for their specific
locale. They would be a little less "snappy" for that other set of
locales but we could have everyone on the same boat more or less.

Is this possible? Acceptable?

best regards,
Armen
Post by Axel Hecht
Hi,
here an update on how we plan to move forward with localizing Firefox
for Android, aka, Fennec. This is the outcome of digesting a ton of
ideas, and a call among Karen, Mark, Brad, Alex, Chris, and I.
The goal is to have a snappy product in a good number of languages by
Firefox 19.
"Snappy" comes with two constraints, startup time and download size.
Download size increases significantly with many localizations added, so
we'll work on reducing that impact. That work is tracked in [1], and is
engineered by the mobile team, with help from build peers, hopefully.
The other half of snappy is startup time, and that means that we can't
afford to have a locale selection independent of the Android settings.
Doing so apparently tears down much of the pre-created android process
and sets it up again, noticably slowing down startup.
That means that the list of locales that we're able to put into the
multi-locale build is limited by what Android supports. This is a
strange feeling for us, but we're going after the users that are on
Android, so that's OK.
The future of the single-locale builds isn't yet determined, but as long
as google play store doesn't support an APK per language, they'll not
prominently exposed. Using them on Nightly or Aurora is fine, though.
Practically, I'll work on separating the localizations that we're
shipping as Firefox from those we're not able to ship (yet) on the
dashboard. There will be one list of languages that go into the
multi-locale build, and that will be offered to sign-off etc, and there
will be the remaining list who'll continue to see builds on aurora and
nightly. This won't affect our builds really, it's just clarifying that
on the l10n dashboard.
Data which locales fall into which bucket are in [2].
We'll test extensively what we can achieve in both size and performance,
and then try to add a healthy amount of localizations to Firefox on
Android.
Thanks for your support and patience, and sorry if the experience we can
create on Android in your language doesn't work out the way we all hoped.
Axel
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=792077
[2]
https://groups.google.com/forum/#!topic/mozilla.dev.platforms.mobile/gAmPESDpfQc
Axel Hecht
2012-09-21 18:50:24 UTC
Permalink
Post by Armen Zambrano G.
Thanks for the clarification and it is understandable.
Can we have in-product selection of a language?
I think it could work like this
* select language
* download whatever strings are needed for that specific locale (not
sure if we have something like a langpack for Android)
** I assume we would fall back on English strings if needed
I assume that people who select a language different than their OS'
would be updated to en-US/multilocale and then immediately after
start-up be retrieving the latest set of string for their specific
locale. They would be a little less "snappy" for that other set of
locales but we could have everyone on the same boat more or less.
Is this possible? Acceptable?
To detail on that:

We can't do language packs without implementing our own localization
story for the native UI.

We can't do language selection differently from the Android locale
selection scheme without regressing startup time.

Axel
Post by Armen Zambrano G.
best regards,
Armen
Post by Axel Hecht
Hi,
here an update on how we plan to move forward with localizing Firefox
for Android, aka, Fennec. This is the outcome of digesting a ton of
ideas, and a call among Karen, Mark, Brad, Alex, Chris, and I.
The goal is to have a snappy product in a good number of languages by
Firefox 19.
"Snappy" comes with two constraints, startup time and download size.
Download size increases significantly with many localizations added, so
we'll work on reducing that impact. That work is tracked in [1], and is
engineered by the mobile team, with help from build peers, hopefully.
The other half of snappy is startup time, and that means that we can't
afford to have a locale selection independent of the Android settings.
Doing so apparently tears down much of the pre-created android process
and sets it up again, noticably slowing down startup.
That means that the list of locales that we're able to put into the
multi-locale build is limited by what Android supports. This is a
strange feeling for us, but we're going after the users that are on
Android, so that's OK.
The future of the single-locale builds isn't yet determined, but as long
as google play store doesn't support an APK per language, they'll not
prominently exposed. Using them on Nightly or Aurora is fine, though.
Practically, I'll work on separating the localizations that we're
shipping as Firefox from those we're not able to ship (yet) on the
dashboard. There will be one list of languages that go into the
multi-locale build, and that will be offered to sign-off etc, and there
will be the remaining list who'll continue to see builds on aurora and
nightly. This won't affect our builds really, it's just clarifying that
on the l10n dashboard.
Data which locales fall into which bucket are in [2].
We'll test extensively what we can achieve in both size and performance,
and then try to add a healthy amount of localizations to Firefox on
Android.
Thanks for your support and patience, and sorry if the experience we can
create on Android in your language doesn't work out the way we all hoped.
Axel
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=792077
[2]
https://groups.google.com/forum/#!topic/mozilla.dev.platforms.mobile/gAmPESDpfQc
Michael Bauer
2012-09-21 19:05:24 UTC
Permalink
Hm there are apps (such as Custom Locale) which simple make Android
believe it's (in my case) Gaelic (which I use to make Opera Mini come up
in Gaelic). It just changes the locale settings, it does not change
anything else and doesn't download stuff or anything and all my date etc
settings are unaffected either.

Could Mobile integrate such a feature i.e. something that allows the
user to choose to "pretend" to be gd-GB or hy-AM or whatever?

Michael
Post by Axel Hecht
We can't do language selection differently from the Android locale
selection scheme without regressing startup time.
Axel
Michael Bauer
2012-09-21 19:11:42 UTC
Permalink
An entirely different question - does an app HAVE to come from the
Marketplace? When testing stuff, such as pre-releases of pred txting for
Gaelic, I got some apk files which I just grapped from a URL and
installed. For those in [2], can't we do install files from the Mozilla
website?

Michael
Post by Axel Hecht
We can't do language packs without implementing our own localization
story for the native UI.
Axel Hecht
2012-09-21 19:34:16 UTC
Permalink
Post by Michael Bauer
An entirely different question - does an app HAVE to come from the
Marketplace? When testing stuff, such as pre-releases of pred txting for
Gaelic, I got some apk files which I just grapped from a URL and
installed. For those in [2], can't we do install files from the Mozilla
website?
You need to set a developer preference on your phone to install stuff
off google play, and the update experience is rather sucky.

Thus the install experience is bad.

See also my comment about the future of the single locale builds not
being determined at this point.

Axel
Post by Michael Bauer
Michael
Post by Axel Hecht
We can't do language packs without implementing our own localization
story for the native UI.
Axel Hecht
2012-09-21 19:35:25 UTC
Permalink
Post by Michael Bauer
Hm there are apps (such as Custom Locale) which simple make Android
believe it's (in my case) Gaelic (which I use to make Opera Mini come up
in Gaelic). It just changes the locale settings, it does not change
anything else and doesn't download stuff or anything and all my date etc
settings are unaffected either.
Could Mobile integrate such a feature i.e. something that allows the
user to choose to "pretend" to be gd-GB or hy-AM or whatever?
I suspect that once you do that, all other apps launch in English? I.e.,
you can't have your phone in Italian, and Firefox in Ligurian?

Axel
Post by Michael Bauer
Post by Axel Hecht
We can't do language selection differently from the Android locale
selection scheme without regressing startup time.
Axel
Michael Bauer
2012-09-21 20:07:30 UTC
Permalink
Interesting, if I use Custom Locale to do any locale (I tried gd-DE,
eu-FR), it always defaults the main UI to English but then it's a UK
phone and that might have something to do with it. Dunno how it would
behave on, say, a German Android phone.

I don't know how I'd go about having the main UI in Italian and Firefox
in Ligurian... grrrr bleeding force locale. But perhaps someone who
knows more about Android than me does?

Michael
Post by Axel Hecht
I suspect that once you do that, all other apps launch in English?
I.e., you can't have your phone in Italian, and Firefox in Ligurian?
Axel
Axel Hecht
2012-09-22 13:21:06 UTC
Permalink
So here's what I expect happens:

You set the phone globally to an unsupported Locale which makes the apps
fall back to the default locale (English), if they're not supporting
that selected locale, which then works for your decided apps.

I don't think that's acceptable as a suggested behavior for Firefox.

Axel
Post by Michael Bauer
Interesting, if I use Custom Locale to do any locale (I tried gd-DE,
eu-FR), it always defaults the main UI to English but then it's a UK
phone and that might have something to do with it. Dunno how it would
behave on, say, a German Android phone.
I don't know how I'd go about having the main UI in Italian and Firefox
in Ligurian... grrrr bleeding force locale. But perhaps someone who
knows more about Android than me does?
Michael
Post by Axel Hecht
I suspect that once you do that, all other apps launch in English?
I.e., you can't have your phone in Italian, and Firefox in Ligurian?
Axel
Michael Bauer
2012-09-22 17:01:07 UTC
Permalink
Well, it wouldn't be a problem for languages where the default locale is
English anyway... but clearly not an elegant solution for the others.

It feels a bit like we're so focussed on an elegant solution that we're
shooting ourselves in the foot by not having the [2] locales at all. You
mentioned there's a startup cost if we set the language from within
Mobile. How big is the delay and would it occur only once when changing
the language or every time the browser is started up? If it's just once
when changing the language, then "who cares"? If I change the language
on Opera Mini, I get an install bar and yes, a delay but at least I get
to where I want to be.

The other thought that crossed my head while gazing across Loch Lomond
this afternoon - you mentioned that the update process sucks (in what
way does it suck, by the way?) if we just hand out apks. Well.. at the
rate at which folk are changing their phones, I'm not entirely sure that
a manual update process is that much of a problem. I'm a troglodyte but
most people I know change their phones on a yearly basis, if not more
often.

Lastly, is there no way we could fudge separate "products" on
marketplace? I admit that I have a limited understanding of Marketplace
but if we can't offer the [2] languages as part of "Mozilla Mobile",
could we not do "Mozilla Mobile Gaelic", "Mozilla Mobile Armenian" etc
as individual products?

Michael
Post by Axel Hecht
You set the phone globally to an unsupported Locale which makes the
apps fall back to the default locale (English), if they're not
supporting that selected locale, which then works for your decided apps.
I don't think that's acceptable as a suggested behavior for Firefox.
Axel
Axel Hecht
2012-09-22 21:07:26 UTC
Permalink
Post by Michael Bauer
Well, it wouldn't be a problem for languages where the default locale is
English anyway... but clearly not an elegant solution for the others.
It feels a bit like we're so focussed on an elegant solution that we're
shooting ourselves in the foot by not having the [2] locales at all. You
mentioned there's a startup cost if we set the language from within
Mobile. How big is the delay and would it occur only once when changing
the language or every time the browser is started up? If it's just once
when changing the language, then "who cares"? If I change the language
on Opera Mini, I get an install bar and yes, a delay but at least I get
to where I want to be.
The other thought that crossed my head while gazing across Loch Lomond
this afternoon - you mentioned that the update process sucks (in what
way does it suck, by the way?) if we just hand out apks. Well.. at the
rate at which folk are changing their phones, I'm not entirely sure that
a manual update process is that much of a problem. I'm a troglodyte but
most people I know change their phones on a yearly basis, if not more
often.
Lastly, is there no way we could fudge separate "products" on
marketplace? I admit that I have a limited understanding of Marketplace
but if we can't offer the [2] languages as part of "Mozilla Mobile",
could we not do "Mozilla Mobile Gaelic", "Mozilla Mobile Armenian" etc
as individual products?
Sorry, but if you want to debate the foundations of our arguments,
you'll need to provide patches and performance measurements.
Speculations don't change the course of action at this point.

Axel
Post by Michael Bauer
Michael
Post by Axel Hecht
You set the phone globally to an unsupported Locale which makes the
apps fall back to the default locale (English), if they're not
supporting that selected locale, which then works for your decided apps.
I don't think that's acceptable as a suggested behavior for Firefox.
Axel
Michael Bauer
2012-09-22 21:36:13 UTC
Permalink
Axel, I assume it wasn't intended to come across as rude as it did... at
least I hope that's the case.

Just because someone is not a programmer who can do patches over
breakfast doesn't mean they can't come up with ideas someone else might
be able to do something with.

Michael
Post by Axel Hecht
Sorry, but if you want to debate the foundations of our arguments,
you'll need to provide patches and performance measurements.
Speculations don't change the course of action at this point.
Axel
Axel Hecht
2012-09-23 16:03:12 UTC
Permalink
Post by Michael Bauer
Axel, I assume it wasn't intended to come across as rude as it did... at
least I hope that's the case.
Just because someone is not a programmer who can do patches over
breakfast doesn't mean they can't come up with ideas someone else might
be able to do something with.
At this point, I disagree with that statement. It took us many failed
good ideas of people like me or Brad Lassey or Mark Finkle, which in the
end died because we couldn't make them work performantly, or at all.

If we were to change plans, the proposal would need to come from someone
that has technical detail and end-to-end understanding of Android of at
least Brad's or Mark's level, plus an idea of the interaction with
gecko. Otherwise we're just burning more time, instead of finally
shipping something.

I'm sorry, but we're done discussing ideas, now we're implementing the
plan we have.

Axel

PS: I replied in short to your previous email, because it was rather
snarky, too.
Post by Michael Bauer
Michael
Post by Axel Hecht
Sorry, but if you want to debate the foundations of our arguments,
you'll need to provide patches and performance measurements.
Speculations don't change the course of action at this point.
Axel
Ibraahiima SAAR
2013-11-06 07:41:01 UTC
Permalink
Hi all,
I have been using Firefox for Android in Fulah for a long time to test my
localization. I installed it on Android in French from "
http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android-l10n/fennec-16.0a2.ff.android-arm.apk".
It worked perfectly and updated almost daily.
But I have noticed that the /latest-mozilla-aurora-android-l10n/ folder is
empty and my Firefox has stopped updating. Worse, I invited a group of
people to help test it in Fulah and I ear unable to fond the Fulah locale
Alla file. That was real annoying...
Can anybody explain what happened? Why can't we have nightly single locale
any more?
Cherts
(A very angry) Ibrahima :-(
Post by Michael Bauer
Axel, I assume it wasn't intended to come across as rude as it did... at
least I hope that's the case.
Just because someone is not a programmer who can do patches over
breakfast doesn't mean they can't come up with ideas someone else might
be able to do something with.
At this point, I disagree with that statement. It took us many failed good
ideas of people like me or Brad Lassey or Mark Finkle, which in the end
died because we couldn't make them work performantly, or at all.

If we were to change plans, the proposal would need to come from someone
that has technical detail and end-to-end understanding of Android of at
least Brad's or Mark's level, plus an idea of the interaction with gecko.
Otherwise we're just burning more time, instead of finally shipping
something.

I'm sorry, but we're done discussing ideas, now we're implementing the plan
we have.

Axel

PS: I replied in short to your previous email, because it was rather
snarky, too.
Post by Michael Bauer
Michael
Post by Axel Hecht
Sorry, but if you want to debate the foundations of our arguments,
you'll need to provide patches and performance measurements.
Speculations don't change the course of action at this point.
Axel
Ibraahiima SAAR
2013-11-06 07:42:46 UTC
Permalink
Sorry for the typos :-)
Post by Ibraahiima SAAR
Hi all,
I have been using Firefox for Android in Fulah for a long time to test my
localization. I installed it on Android in French from "
http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android-l10n/fennec-16.0a2.ff.android-arm.apk".
It worked perfectly and updated almost daily.
But I have noticed that the /latest-mozilla-aurora-android-l10n/ folder is
empty and my Firefox has stopped updating. Worse, I invited a group of
people to help test it in Fulah and I ear unable to fond the Fulah locale
Alla file. That was real annoying...
Can anybody explain what happened? Why can't we have nightly single
locale any more?
Cherts
(A very angry) Ibrahima :-(
Post by Michael Bauer
Axel, I assume it wasn't intended to come across as rude as it did... at
least I hope that's the case.
Just because someone is not a programmer who can do patches over
breakfast doesn't mean they can't come up with ideas someone else might
be able to do something with.
At this point, I disagree with that statement. It took us many failed good
ideas of people like me or Brad Lassey or Mark Finkle, which in the end
died because we couldn't make them work performantly, or at all.
If we were to change plans, the proposal would need to come from someone
that has technical detail and end-to-end understanding of Android of at
least Brad's or Mark's level, plus an idea of the interaction with gecko.
Otherwise we're just burning more time, instead of finally shipping
something.
I'm sorry, but we're done discussing ideas, now we're implementing the
plan we have.
Axel
PS: I replied in short to your previous email, because it was rather
snarky, too.
Post by Michael Bauer
Michael
Post by Axel Hecht
Sorry, but if you want to debate the foundations of our arguments,
you'll need to provide patches and performance measurements.
Speculations don't change the course of action at this point.
Axel
_______________________________________________
dev-l10n mailing list
https://lists.mozilla.org/listinfo/dev-l10n
Axel Hecht
2013-11-06 12:24:20 UTC
Permalink
Filed https://bugzilla.mozilla.org/show_bug.cgi?id=935463, this is a
regression that made it across merge day.

Axel
Post by Ibraahiima SAAR
Hi all,
I have been using Firefox for Android in Fulah for a long time to test my
localization. I installed it on Android in French from "
http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android-l10n/fennec-16.0a2.ff.android-arm.apk".
It worked perfectly and updated almost daily.
But I have noticed that the /latest-mozilla-aurora-android-l10n/ folder is
empty and my Firefox has stopped updating. Worse, I invited a group of
people to help test it in Fulah and I ear unable to fond the Fulah locale
Alla file. That was real annoying...
Can anybody explain what happened? Why can't we have nightly single locale
any more?
Cherts
(A very angry) Ibrahima :-(
Post by Michael Bauer
Axel, I assume it wasn't intended to come across as rude as it did... at
least I hope that's the case.
Just because someone is not a programmer who can do patches over
breakfast doesn't mean they can't come up with ideas someone else might
be able to do something with.
At this point, I disagree with that statement. It took us many failed good
ideas of people like me or Brad Lassey or Mark Finkle, which in the end
died because we couldn't make them work performantly, or at all.
If we were to change plans, the proposal would need to come from someone
that has technical detail and end-to-end understanding of Android of at
least Brad's or Mark's level, plus an idea of the interaction with gecko.
Otherwise we're just burning more time, instead of finally shipping
something.
I'm sorry, but we're done discussing ideas, now we're implementing the plan
we have.
Axel
PS: I replied in short to your previous email, because it was rather
snarky, too.
Post by Michael Bauer
Michael
Post by Axel Hecht
Sorry, but if you want to debate the foundations of our arguments,
you'll need to provide patches and performance measurements.
Speculations don't change the course of action at this point.
Axel
_______________________________________________
dev-l10n mailing list
https://lists.mozilla.org/listinfo/dev-l10n
Archaeopteryx
2012-09-22 14:37:13 UTC
Permalink
How many active daily installations of Fennec will be affected by this
(in total and as % of our userbase)? How will languages be treated which
are available only on some devices (either added by vendor or OS like
Cyanogenmod)?

Thank you
Archaeopteryx

-------- Original-Nachricht --------
Betreff: Firefox for Android localization update
Von: Axel Hecht <***@mozilla.com>
An:
Datum: 2012-09-21 16:57
Post by Axel Hecht
Hi,
here an update on how we plan to move forward with localizing Firefox
for Android, aka, Fennec. This is the outcome of digesting a ton of
ideas, and a call among Karen, Mark, Brad, Alex, Chris, and I.
The goal is to have a snappy product in a good number of languages by
Firefox 19.
"Snappy" comes with two constraints, startup time and download size.
Download size increases significantly with many localizations added, so
we'll work on reducing that impact. That work is tracked in [1], and is
engineered by the mobile team, with help from build peers, hopefully.
The other half of snappy is startup time, and that means that we can't
afford to have a locale selection independent of the Android settings.
Doing so apparently tears down much of the pre-created android process
and sets it up again, noticably slowing down startup.
That means that the list of locales that we're able to put into the
multi-locale build is limited by what Android supports. This is a
strange feeling for us, but we're going after the users that are on
Android, so that's OK.
The future of the single-locale builds isn't yet determined, but as long
as google play store doesn't support an APK per language, they'll not
prominently exposed. Using them on Nightly or Aurora is fine, though.
Practically, I'll work on separating the localizations that we're
shipping as Firefox from those we're not able to ship (yet) on the
dashboard. There will be one list of languages that go into the
multi-locale build, and that will be offered to sign-off etc, and there
will be the remaining list who'll continue to see builds on aurora and
nightly. This won't affect our builds really, it's just clarifying that
on the l10n dashboard.
Data which locales fall into which bucket are in [2].
We'll test extensively what we can achieve in both size and performance,
and then try to add a healthy amount of localizations to Firefox on
Android.
Thanks for your support and patience, and sorry if the experience we can
create on Android in your language doesn't work out the way we all hoped.
Axel
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=792077
[2]
https://groups.google.com/forum/#!topic/mozilla.dev.platforms.mobile/gAmPESDpfQc
Axel Hecht
2012-09-22 21:09:52 UTC
Permalink
Post by Archaeopteryx
How many active daily installations of Fennec will be affected by this
(in total and as % of our userbase)? How will languages be treated which
are available only on some devices (either added by vendor or OS like
Cyanogenmod)?
None of our installations of Firefox on Android will be affected. We'll
only be extending the reach of localizations.

Regarding vendor- or mod-specific languages, do you have a list? Without
such a list, it's hard to tell how much of a problem this really is.

Axel
Post by Archaeopteryx
Thank you
Archaeopteryx
-------- Original-Nachricht --------
Betreff: Firefox for Android localization update
Datum: 2012-09-21 16:57
Post by Axel Hecht
Hi,
here an update on how we plan to move forward with localizing Firefox
for Android, aka, Fennec. This is the outcome of digesting a ton of
ideas, and a call among Karen, Mark, Brad, Alex, Chris, and I.
The goal is to have a snappy product in a good number of languages by
Firefox 19.
"Snappy" comes with two constraints, startup time and download size.
Download size increases significantly with many localizations added, so
we'll work on reducing that impact. That work is tracked in [1], and is
engineered by the mobile team, with help from build peers, hopefully.
The other half of snappy is startup time, and that means that we can't
afford to have a locale selection independent of the Android settings.
Doing so apparently tears down much of the pre-created android process
and sets it up again, noticably slowing down startup.
That means that the list of locales that we're able to put into the
multi-locale build is limited by what Android supports. This is a
strange feeling for us, but we're going after the users that are on
Android, so that's OK.
The future of the single-locale builds isn't yet determined, but as long
as google play store doesn't support an APK per language, they'll not
prominently exposed. Using them on Nightly or Aurora is fine, though.
Practically, I'll work on separating the localizations that we're
shipping as Firefox from those we're not able to ship (yet) on the
dashboard. There will be one list of languages that go into the
multi-locale build, and that will be offered to sign-off etc, and there
will be the remaining list who'll continue to see builds on aurora and
nightly. This won't affect our builds really, it's just clarifying that
on the l10n dashboard.
Data which locales fall into which bucket are in [2].
We'll test extensively what we can achieve in both size and performance,
and then try to add a healthy amount of localizations to Firefox on
Android.
Thanks for your support and patience, and sorry if the experience we can
create on Android in your language doesn't work out the way we all hoped.
Axel
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=792077
[2]
https://groups.google.com/forum/#!topic/mozilla.dev.platforms.mobile/gAmPESDpfQc
Continue reading on narkive:
Loading...