public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] manual: Add more documentation for the tm_isdst member of struct tm
Date: Thu, 27 Oct 2022 12:09:24 +0200	[thread overview]
Message-ID: <87ilk5r31n.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <6b01632f-047c-c18f-5616-4037bfe706fa@cs.ucla.edu> (Paul Eggert's message of "Wed, 26 Oct 2022 12:05:07 -0700")

* Paul Eggert:

>> Maybe we should just document that applications should set this field to
>> -1 when constructing struct tm data?
>
> Yes, if you're deriving struct tm data from the outside world and you
> have no idea what tm_isdst etc. should be, your apps should set
> tm_isdst to -1. However, if the outside world tells you tm_gmtoff
> (which is pretty common these days, e.g., see the "Date:" line in this
> email), then your apps should also set tm_gmtoff to what the outside
> world tells you, before you call mktime.

Okay, that would indeed be helpful advice.  I'll see if I can come up
with a new patch.

>> In case of Ireland it seems an artificial complication, though.  The
>> perception seems to be that IST is summer time, not standard time
>
> My impression is different, in that people in Ireland typically say
> "summer time" or "winter time". They typically do not say "standard 
> time" or "daylight saving time". And as it happens, summer time =
> standard time in Ireland.

I think RTE is not exactly fringe media in Ireland, and they recently
wrote (largely copying from last year I admittedly):

| When do the clocks change in Ireland in 2022?
|
| Daylight saving time in Ireland began (went forward an hour) at 01:00
| on Sunday, 27 March 2022 and will end (go back an hour) at 02:00 on
| Sunday, 30 October 2022.

<https://www.rte.ie/lifestyle/living/2022/0309/1285354-everything-you-need-to-know-about-the-clocks-changing-in-2022/>

This is not just one journalist making an error.  I think the cultural
convention *is* different.

Thanks,
Florian


      reply	other threads:[~2022-10-27 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 12:51 Florian Weimer
2022-10-24 19:44 ` Paul Eggert
2022-10-24 21:13   ` Florian Weimer
2022-10-25 17:49     ` Paul Eggert
2022-10-25 18:07       ` Florian Weimer
2022-10-25 18:27         ` Paul Eggert
2022-10-26 11:21           ` Florian Weimer
2022-10-26 19:05             ` Paul Eggert
2022-10-27 10:09               ` Florian Weimer [this message]

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=87ilk5r31n.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.org \
    /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).