From: lyndsay <lyndsay@vivaldi.net>
To: 9front@9front.org
Subject: Re: [9front] quick tmdate question
Date: Fri, 1 Oct 2021 08:24:53 -0600 [thread overview]
Message-ID: <c4d1ed21-d624-80c9-6361-c169fe820c05@vivaldi.net> (raw)
In-Reply-To: <AD48C30A020D4C6BB91161CAEA3C4AC8@eigenstate.org>
awesome, that should be fine for me; all of the times being processed=20
have to be put in by the user and the users probably won't want to use a=20
calendar other than gregorian so almost all input, even before 1582,=20
would probably end up being in proleptic gregorian format anyway. at=20
least, that's what the mathematical equations i put in are assuming!=20
i'll also put a note in the help and manual for the software juuuust to=20
make sure.
thanks!
lyndsay
On 9/30/21 23:15, ori@eigenstate.org wrote:
> Quoth lyndsay <lyndsay@vivaldi.net>:
>> can't find a clear answer in tmdate(2)=C2=A0 - i'm writing a program (=
in c)
>> that needs a way to store and parse any arbitrary time AD. will those =
be
>> properly dealt with if i store times in Tm and parse user input with
>> tmparse() or should i write my own function?
> If the proleptic gregorian calendar is enough, then
> tmdate should work for you. It does not handle the
> (locale-specific!) calendar changeovers. Our timezone
> information simply doesn't encode calendar changes.
>
> I'm not even sure if the IANA timezone database encodes
> calendar changes.
>
> I'd suggest using the proleptic gregorian calendar, and
> converting from it as late as possible. Ideally never.
>
> https://en.wikipedia.org/wiki/List_of_adoption_dates_of_the_Gregorian_c=
alendar_by_country
>
prev parent reply other threads:[~2021-10-02 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 15:05 lyndsay
2021-10-01 1:54 ` Kurt H Maier
2021-10-01 5:15 ` ori
2021-10-01 14:24 ` lyndsay [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=c4d1ed21-d624-80c9-6361-c169fe820c05@vivaldi.net \
--to=lyndsay@vivaldi.net \
--cc=9front@9front.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 NNTP newsgroup(s).