From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from icebubble.org ([174.136.103.210]) by ewsd; Tue May  5 16:03:43 EDT 2020
Received: from petunia by icebubble.org with local-bsmtp (Exim 4.76)
	(envelope-from <magma698hfsp273p9f@icebubble.org>)
	id 1jW3n4-0003d2-FF
	for 9front@9front.org; Tue, 05 May 2020 20:03:42 +0000
Received: from rusat by cmarib.ramside with local (Exim 4.72)
	(envelope-from <magma698hfsp273p9f@icebubble.org>)
	id 1jW1No-0006he-0K
	for 9front@9front.org; Tue, 05 May 2020 17:29:28 +0000
From: magma698hfsp273p9f@icebubble.org
To: 9front@9front.org
Subject: Re: [9front] Re: Date and time handling.
References: <1CE411CAAB15E7AEBECDD117C02455EB@eigenstate.org>
Date: Tue, 05 May 2020 17:29:26 +0000
In-Reply-To: <1CE411CAAB15E7AEBECDD117C02455EB@eigenstate.org>
	(ori@eigenstate.org's message of "Sun, 3 May 2020 21:08:04 -0700")
Message-ID: <86y2q6ffyh.fsf@cmarib.ramside>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: social lossless metadata-aware control 

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