Bugzilla

I'm really not sure -- it's a tough issue. In principle, I'd strongly prefer us to ship all the intl data for all locales. But I realize that may be prohibitive, and come with its own drawbacks, e.g. if the increased download size significantly reduces adoption.

Next-best option might be on-demand addition of locale data, so that we'd ship with data for just a "core" set of locales, but Firefox would fetch additional locales on the fly in response to content or script asking to use them. So the first time someone does `today.toLocaleDateString("snd")`, we'd install the Sindhi locale data and it'd "just work" for those users. But that's technically challenging, I'm sure (particularly for sync APIs), and we may not have the developer resources to do it at this point.

So yes, I might end up agreeing with (1), reluctantly; but I wasn't comfortable with it being discussed in terms of such a marginal example, which I don't think gave a fair impression of the impact. As for (2), I don't know where to draw the line, but I'm uneasy about dropping support for a language as major as "snd".

Maybe we need to brainstorm some more criteria for inclusion? A couple of ideas we could consider:
* Any locale that is a national/official language of a country or a major region (province, state, whatever) gets kept
   - So that would include "snd", as the official language of Sindh province in Pakistan, as well as one of the official [scheduled languages](https://en.wikipedia.org/wiki/Languages_with_official_status_in_India) of India
   - It would also include "dv", which only has 340K speakers but is the official language of the Maldives 
* Any locale with more than X speakers, where X is.... 100K? A million? Ten million? I don't know... wdyt?
   - This would include examples like "srk", with 20 million speakers

There are probably other useful criteria... e.g. are there regular newspapers published in the language? Used in regular television broadcasting? Other ideas...?

I'm really not sure -- it's a tough issue. In principle, I'd strongly prefer us to ship all the intl data for all locales. But I realize that may be prohibitive, and come with its own drawbacks, e.g. if the increased download size significantly reduces adoption.

Next-best option might be on-demand addition of locale data, so that we'd ship with data for just a "core" set of locales, but Firefox would fetch additional locales on the fly in response to content or script asking to use them. So the first time someone does `today.toLocaleDateString("snd")`, we'd install the Sindhi locale data and it'd "just work" for those users. But that's technically challenging, I'm sure (particularly for sync APIs), and we may not have the developer resources to do it at this point.

So yes, I might end up agreeing with (1), reluctantly; but I wasn't comfortable with it being discussed in terms of such a marginal example, which I don't think gave a fair impression of the impact. As for (2), I don't know where to draw the line, but I'm uneasy about dropping support for a language as major as "snd".

Maybe we need to brainstorm some more criteria for inclusion? A couple of ideas we could consider:
* Any locale that is a national/official language of a country or a major region (province, state, whatever) gets kept
   - So that would include "snd", as the official language of Sindh province in Pakistan, as well as one of the official [scheduled languages](https://en.wikipedia.org/wiki/Languages_with_official_status_in_India) of India
   - It would also include "dv", which only has 340K speakers but is the official language of the Maldives 
* Any locale with more than X speakers, where X is.... 100K? A million? Ten million? I don't know... wdyt?
   - This would include examples like "skr", with 20 million speakers

There are probably other useful criteria... e.g. are there regular newspapers published in the language? Used in regular television broadcasting? Other ideas...?