>> As a result, if we have a timestamp like this: >> >> Jan 1 2013, 7:00 PM EST >> >> will not be able to deal with the timezone component. > > And now that I've started poking at converting code like > seconds(1), it looks like I'm going to need to solve it. > I'm thinking that I want to add /adm/timezone/abbrev, > which would look like: > > EST US_Eastern > PST US_Pacific > AEST Australia_Tasmania > > Obviously, this is a lossy mapping: There are multiple > named timezones that map to one abbreviation, and I think > that's fine.
Hm. And looking again at the relevant standards, rfc5322 only allows a short list of US timezone names, and rfc8601 doesn't allow any. Perhaps the appropriate solution is to hard code the American timezones, and reject all other abbreviations, as in rfc5322. I don't like the lack of generality, but it's an option. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T5b9f56a5fac852c2-M65b891ded6fa1c50e84c061c Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
