https://bugzilla.redhat.com/show_bug.cgi?id=1133188

--- Comment #34 from Siddhesh Poyarekar spoyarek@redhat.com --- (In reply to Ani Peter from comment #30)

Also a kind request is that when an existing feature/setting (esp sensitive like this) receives a feedback or a bug get reported like this, ideally it should be taken up for discussion with wider crowd, language communities and decided upon concensus. It should not be that a bug is reported and change is done. That wrong approach is something that has made all feel bad.

Why is filing a bug report the 'wrong' approach? You cannot expect every user to try and figure out the mailing list for the localization team and open a conversation with them for everything that they think might be wrong.

(In reply to Ankit Patel from comment #32)

You might want to analyze the *facts* (not assumptions) posted/discussed in this bug and make your decision.

Again, speaking a certain language and using it on a computer on a regular basis are two completely different things. See slide 10 on [1] for example, which says only 12% of urban users use computing devices in any language other than English.

I don't ask to go by that study because it is not necessarily representative of the entire population - it has the known limitation of sampling only urban computer users and their sample size of 65000 is not large enough to be representative IMO. Look for facts like those when you're deciding on default selections and not just a count of how many users speak a certain language natively.

If you conclude that there are in fact no such studies that can be relied upon then state that explicitly and then make a decision based on a fallback such as overall language demographics.

[1] http://www.slideshare.net/JuxtConsult/toplines-of-india-bytes-a-computer-usa...