2 ms·
Thanks; that is what I was looking for. Last time I had to work in detail with timezones (with the above reqs, plus some others), that didn't exist (based on th
by lostcolony 5y ago
Thanks; that is what I was looking for. Last time I had to work in detail with timezones (with the above reqs, plus some others), that didn't exist (based on the date for the RFC).
As to having to/not having to implement this (and rely on the OS) - probably! I just know at the time I last dealt with this, every library I could find packaged their own TZ DB, and they were definitely not standard.
- Macha 5y agoWhich RFC? The RFC moving it to IANA in 2012? It's been in development in some way since the 80s [1], the current timezone names in it are from the 90s[2], and it was definitely already the standard timezone definitions when I started using Linux in the 00s. [1]: http://mm.icann.org/pipermail/tz/1986-November/008946.html http://mm.icann.org/pipermail/tz/1986-November/008946.html [2]: https://mm.icann.org/pipermail/tz/1993-October/009233.html https://mm.icann.org/pipermail/tz/1993-October/009233.html
- lostcolony 5y agoYes, moving it to IANA. Maybe the packaged DBs were 'standard', in a sense, but you couldn't just take a file from one and drop it into another; they were configured or serialized in various ways. Regardless, it meant updating a dependency when things changed; I don't know the state of historical timezone information at the OS level at that time, but I do know none of the libraries I looked at made OS calls.
- mark-r 5y agoAccording to Wikipedia the database was started in 1986 or earlier; it was known as the Olson database. https://en.wikipedia.org/wiki/Tz_database#History https://en.wikipedia.org/wiki/Tz_database#History