Greetings, Corinna Vinschen! >> Should I change the locale setting or the LC_TIME or TZ? >> I tried setting : >> set env `locale -f en_IN.utf8` >> but cygwin says : >> Environment variable env `locale -f en_IN.utf8` not defined >> tzset: can't find matching POSIX timezone for Windows timezone "India >> standard time"
> Uh oh. Why on earth is the string returned by your machine in lower > case?!? The default Windowes timezone name is "India Standard Time" > with upper case S and T. > The tzset application checks the value returned by the OS > case-sensitive, so, yes, it just doesn't recognize the string and fails > to set the matching POSIX timezone. > Crazy but true: After all this time it's the first report that tzset > fails because some Windows system returns timezones in different case. It is trivial to edit the name of timezone in registry. Which was likely done in this case. According to Microsoft's TZEDIT utility[1], the name of the timezone IS, indeed, "India Standard Time", with proper capitalization as of current Microsoft timezone update. Even if it is not, on certain system, for some reason, this is a problem that can be resolved using the same aforementioned utility. > I'm going to fix the tzset tool to use case-insensitve string checks. I doubt it is necessary. > I'm also going to upload a new Cygwin test release, 2.1.0-0.5, which > will contain the fixed tzset tool. I'll announce it later today. > Please give it a try. [1] http://download.microsoft.com/download/5/8/a/58a208b7-7dc7-4bc7-8357-28e29cdac52f/TZEDIT.exe -- With best regards, Andrey Repin Wednesday, July 8, 2015 16:49:51 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
