nayarsystems/posix_tz_db

Generates POSIX timezones strings

posix_tz_db's Issues

GMT+2 and GMT-2 are swapped

Hi, in my code I set timezone to GMT+2 which is Sweden time(UTC+2), but it shows wrong time. Only when I changed it to GMT-2, it is correct.

Issue with recent zoneinfo updates

Hello,
Africa/ Casablanca and El_Aaiun both return an empty string.
It seems zoneinfo format has changed for these two cities.

America/Nuuk missing

The python code has a hard coded list of the files to inspect. America/Godthab was renamed to America/Nuuk in 2020a, but the list is not updated. Both names should be in the list, or Godthab changed to Nuuk.

On Linux Mint 19.3, /usr/share/zoneinfo/America/Nuuk -> Godthab

"Release 2020a - 2020-04-23 16:03:47 -0700... America/Nuuk renamed from America/Godthab. ..."

(Thanks! I'm using this after using https://github.com/evansiroky/timezone-boundary-builder (that's where Nuuk came from) to make a map of lat/lon to TZ pixels. A GPS synced clock uses the map to get local time on ESP32. The ESP32 understands the zone descriptions but not the names. It packs nicely into <2MB with ~1 mile resolution.)

America/Nuuk missing

The python code has a hard coded list of the files to inspect. America/Godthab was renamed to America/Nuuk in 2020a, but the list is not updated. Both names should be in the list, or Godthab changed to Nuuk.

On Linux Mint 19.3, /usr/share/zoneinfo/America/Nuuk -> Godthab

"Release 2020a - 2020-04-23 16:03:47 -0700... America/Nuuk renamed from America/Godthab. ..."

(Thanks! I'm using this after using https://github.com/evansiroky/timezone-boundary-builder (that's where Nuuk came from) to make a map of lat/lon to TZ pixels. A GPS synced clock uses the map to get local time on ESP32. The ESP32 understands the zone descriptions but not the names. It packs nicely into <2MB with ~1 mile resolution.)

Europe/London entry is wrong

Europe/London GMT0BST,M3.5.0/1,M10.5.0

Should be:

Europe/London GMT0BST,M3.4.0/1,M10.4.0

UK always uses 4th Sunday in March and October

Fiji has a bad DST end time

Pacific/Fiji has a DST end time of 147 (should be 3?)

Asia/Tehran format should not use 'J'

Currently Tehran has entry:
"Asia/Tehran","<+0330>-3:30<+0430>,J80/0,J264/0"
I believe it should be
"Asia/Tehran","<+0330>-3:30<+0430>,80/0,264/0"

From http://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html

Jn
This specifies the Julian day, with n between 1 and 365. February 29 is never counted, even in leap years.

n
This specifies the Julian day, with n between 0 and 365. February 29 is counted in leap years.

From https://en.wikipedia.org/wiki/Iran_Standard_Time:

The Iranian DST starts on March 22 and ends on September 22 each year with the exception of leapyears in which the DST starts and ends one day prior.

Year | DST Start Date and Time | DST End Date and Time
-- | -- | --
2014 | Sat, Mar 22, 0:00 AM | Mon, Sep 22, 0:00 AM
2015 | Sun, Mar 22, 0:00 AM | Tue, Sep 22, 0:00 AM
2016 | Mon, Mar 21, 0:00 AM | Wed, Sep 21, 0:00 AM
2017 | Wed, Mar 22, 0:00 AM | Fri, Sep 22, 0:00 AM
2018 | Thu, Mar 22, 0:00 AM | Sat, Sep 22, 0:00 AM

This mean Feb 29. should be counted. No 'J'.
I'm calculating Mar 21, not Mar with the current format, because the count starts a 1. Counting from 0, will result in Mar 22 (and Mar 21 on a leap year)

Copyright details are missing in the LICENSE

The LICENSE does not have name and year. Can you add those?

Paraguay time

Today 4/10/2020 we had a change to 1 hour more
<-04>4<-03>,M10.1.0/0,M3.4.0/0 did not change time ...it is still the old time