On 10/15/2013 1:50 PM, Anne van Kesteren wrote:
As far as JavaScript API features go, I don't think we should vary our
offering by locale. E.g. for Firefox OS we want changing locale to
just work and not require a new version of Firefox OS. The same goes
for a computer in a hotel or hostel or some such. Firefox should work
for each locale users might have set in Gmail.
And yet, we don't ship by default a version of Firefox that has all the
languages in it, even though that would be good for those use cases also.
If it didn't cost us anything to include all languages, I wouldn't be
harping on this. But we know that increased package sizes cost us
Firefox desktop adoption. So what would the practical effect be of only
including the English data files in the English Firefox, and so forth,
and allowing users to get additional ICU data via langpacks, the same
way we get a Firefox translation?
Is there a primary use case for supporting these Intl APIs for languages
that a user normally doesn't see?
--BDS
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
