From: magma698hfsp273p9f@icebubble.org
To: 9front@9front.org
Subject: Re: [9front] Re: Date and time handling.
Date: Tue, 05 May 2020 17:29:26 +0000 [thread overview]
Message-ID: <86y2q6ffyh.fsf@cmarib.ramside> (raw)
In-Reply-To: <1CE411CAAB15E7AEBECDD117C02455EB@eigenstate.org> (ori@eigenstate.org's message of "Sun, 3 May 2020 21:08:04 -0700")
ori@eigenstate.org writes:
> One thing that will annoy me: Currently, you need to specify the timezone
> as the filename, eg, "US_Eastern", rather than as the well known name,
> eg, "EST". There are two reasons for this.
>
> 1) We have no way to map from a timezone to the name, other than
> opening each timezone file and reading the first line.
>
> 2) The timezone name that we store in those files is wrong. We only
> have 3 characters for the timezone, so "Australia_Tasmania" becomes
> EST instead of AEST.
>
> I can hard-code a mapping, but that kind of sucks. I'd like to parse
> the IANA timezone database and generate files instead, either with a
> separate 'tzmap' file, or with duplicates for the abbreviated zones
> that we can open directly.
# hm... why not use ndb? file=... to split the db among multiple files
tzfs -f /ndb/timezone /srv/tzfs
mount /srv/tzfs /adm/timezone
> RFC3339:
> YYYY-01-DDThh:mm:ss[Z]ZZ
More human-readable variants of RFC3339:
YYYY-MM-DD hh:mm:ss
YYYY-MM-DD hh:mm:ss Z
YYYY-MM-DD hh:mm:ss z
YYYY-MM-DD hh:mm:ss 0
YYYY-MM-DD hh:mm:ss +0400
YYYY-MM-DD hh:mm:ss -0400
YYYY-MM-DD hh:mm:ss +5
YYYY-MM-DD hh:mm:ss -0
YYYY-MM-DD @ hh:mm:ss
YYYY-MM-DD @ hh:mm:ss +830
YYYY-MM-DD @ hh:mm:ss -0315
YYYY-MM-DD @ hh:mm:ss -3
YYYY-MM-DD @ hh:mm:ss +0
YYYY-MM-DD @ hh:mm:ss 0000
prev parent reply other threads:[~2020-05-05 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 3:56 ori
2020-04-08 6:48 ` [9front] " Steve Simon
2020-04-09 14:12 ` ori
2020-04-12 6:20 ` ori
2020-04-12 18:27 ` magma698hfsp273p9f
2020-04-13 0:36 ` [9front] " ori
2020-04-16 20:40 ` ori
2020-05-04 4:08 ` ori
2020-05-05 17:29 ` magma698hfsp273p9f [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=86y2q6ffyh.fsf@cmarib.ramside \
--to=magma698hfsp273p9f@icebubble.org \
--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).