On Mar 23 10:38, Brian Inglis via Cygwin-apps wrote:
> It looks to me that tzset.c prioritizes the Windows label over the country,
> and it may be a better match prioritizing the country over the label, if the
> country is not 001/"", nor ZZ, which are the generic entries.
The Windows timezone is the relevant setting in the first place becasue
that's what indicvates the actual local time *as the user chose*.
The territory should only be a secondary hint to choose the right
POSIX entry.
For instance, I know people always using UTC, independently of their
territory setting. If the territory rules, this user choice would be
broken in Cygwin.
> It also is not clear what tzset should do when tzmap has a list of zones to
> choose from, for example:
>
> { L"Mountain Standard Time", L"CA", L"America/Edmonton
> America/Cambridge_Bay America/Inuvik" },
> { L"Mountain Standard Time", L"US", L"America/Denver America/Boise" },
> { L"US Mountain Standard Time", L"CA", L"America/Creston
> America/Dawson_Creek America/Fort_Nelson" },
>
> it currently just prints the first, but perhaps it should print all relevant
> entries and the caller should handle the alternatives?
tzset is called from the shell default profile. It has to use exactly
one, valid entry, so time works as desired without forcing interactivity.
If the user doesn't like it, the user can always override tzset's choice
in her own profile.
Corinna
