On Thu 20 Jun 2024 at 21:00:38 (+1000), Keith Bainbridge wrote: > On 17/6/24 18:26, Keith Bainbridge wrote: > > > > It was late afternoon on 16Jun2024 that I wrote this. Possibly > > 18:13:36 when I pressed send. I'd reckon it would likely have been > > 08:13:36 UTC What's wrong with my system clock. I've not really > > looked at the time on my originals before. I'll try to remember > > to enter my local time as I press send > > Thanks for those responses. [ … ] > > I reskon that they seem to indicate that the date/time in my original > question are fine. the difficulty is more related to how we humans are > interpreting the information we are reading. > > https://manpages.debian.org/bookworm/manpages-dev/strftime.3.en.html > > is a list of place names for MANY parts of a date layout. I have set > up the following code in my text substitution app: > "%a %d%b%Y at %H:%M:%S =UTC %Z" > > Triggering that give me > Thu 20Jun2024 at 20:51:19 =UTC +10:00 > > Seems to me that if the code writers of our various MUA would add the > +UTC to the line that prints the various dates, we'd understand what > they mean better. > > Meantime, we have to accept what we have.
You could pronounce your time written above as: "It's Thu 20Jun2024 at 20:51:19 here, where clocks are UTC+10:00" if that's indeed your intention. But what you've done is invent some notation of your own, which people will likely misunderstand. I think it best to look up these references and follow them: https://en.wikipedia.org/wiki/ISO_8601 https://www.ietf.org/rfc/rfc3339.txt IMHO I think that email attributions are best presented in and with the time zone of the sender, and not oneself. Cheers, David.
