9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: steve@quintile.net, 9front@9front.org
Subject: Re: [9front] Date and time handling.
Date: Thu, 9 Apr 2020 07:12:42 -0700	[thread overview]
Message-ID: <C0E12E8C6FB4CBAECF28D466AB6064F6@eigenstate.org> (raw)
In-Reply-To: <43B494B5-78E6-4967-ACE5-289ADD02CD2F@quintile.net>

> well done!
> 
> i tried to do this years ago whilst writing an ical parser - and gave up in horror.
> 
> -Steve
> 

I should probably be absolutely clear: the manpage is aspirational, not
documentational, though I think the hard parts are done or close.

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.



  reply	other threads:[~2020-04-09 14:12 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 [this message]
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

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=C0E12E8C6FB4CBAECF28D466AB6064F6@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    --cc=steve@quintile.net \
    /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).