Description of problem: during installation in Punjabi (Indian Language), default selected Time zone was US/NewYork, but it should be Calcuta Version-Release number of selected component (if applicable): anaconda-11.2.0.19-1.x86_64.rpm How reproducible: Everytime during install in Punjabi Steps to Reproduce: 1. Select Installation in Punjabi 2. Move forward till Time zone reach 3. Actual results: it is US/NewYork Expected results: should Asia/Calcuta (India) Additional info: using following build rawhide-20070206
While for some languages it might be quite clear the connection between the Language and a good guess at the location, is this something we can actually do in the general case, without causing nightmares? What would happen if we selected timezones based on a language shared between two countries that object to the other? We will quickly have nobody happy. Personally I think the default should be UTC until the map is clicked.
it is based on locale, as pa_IN is represent Punjabi_India, where *_IN is limiting the area as India, and so timezone is clearly 1 and only 1 Calcutta.
Sure, but should en_AU be Sydney, Adelaide or Perth? Should en_US be east or west coast? I still argue you can't win...
I think bug was only for pa_IN, not going to consider en_AU as it is very far from my city
This will be fixed in the next release of anaconda. It affects at least all languages that anaconda cannot display during the initial stage.