public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [tz] Ubuntu drops old-style links
Date: Sat, 23 Mar 2024 22:11:27 +0100	[thread overview]
Message-ID: <Zf9FfzT2zWm1bFIN@calimero.vinschen.de> (raw)
In-Reply-To: <a2cb9a61-2434-4093-8833-c89d22f8b0f7@SystematicSW.ab.ca>

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

  parent reply	other threads:[~2024-03-23 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKxAwDomYU4=EOyMXTUcgDQJp0k7jQncRSChGB86xHT+9+hucA@mail.gmail.com>
     [not found] ` <86ff5be5-ccae-4bc0-81af-46abc54e549d@systematicsw.ab.ca>
2024-03-20 20:59   ` Fwd: " Brian Inglis
2024-03-21  9:36     ` Corinna Vinschen
2024-03-22 16:02       ` Brian Inglis
2024-03-22 20:02         ` Brian Inglis
2024-03-22 20:10         ` Brian Inglis
2024-03-23  9:54         ` Corinna Vinschen
2024-03-23 16:38           ` Brian Inglis
2024-03-23 18:54             ` Brian Inglis
2024-03-23 21:11             ` Corinna Vinschen [this message]
2024-03-28  8:25               ` [tz] Ubuntu drops old-style links - tzdata split test package Brian Inglis
2024-03-28 10:13                 ` Corinna Vinschen
2024-03-28 18:35                   ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zf9FfzT2zWm1bFIN@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).