- tz - lists.iana.org

Tocantins is not going to observe DST in 2013/2014
by Alexander Krivenyshev Oct. 1, 2013

Oct. 1, 2013

According to the news, http://portal.to.gov.br/ http://g1.globo.com/to/tocantins/noticia/2013/09/governo-federal-confirma- exclusao-do-tocantins-do-horario-de-verao.html http://economia.estadao.com.br/noticias/economia-geral,governo-exclui- tocantins-do-horario-de-verao,166052,0.htm Tocantins, Brazil is not going to observe DST. Brazil government issued a decision that excludes the Tocantins from DST. (translation from Portuguese) It was published in extra edition of the Official Gazette on Monday, September 30 2013, confirmed the exclusion of Tocantins DST in 2013/2014, Decree No. 6558, in Article 2, that "summer time will be in force in the following states : Rio Grande do Sul, Santa Catarina, Paraná, São Paulo, Rio de Janeiro, Espírito Santo, Minas Gerais, Goiás, Mato Grosso, Mato Grosso do Sul and the Federal District. Tocantins was excluded from the list. Alexander Krivenyshev- WorldTimeZone.com

1 0

Re: [tz] [tz-announce] tzcode2013g and tzdata2013g available
by Young, Steven Oct. 1, 2013

Oct. 1, 2013

Lets run this SOP to validate this, but we need a better / clearer SOP and automated process. J. Steven Young Technology Manager | Orbitz Worldwide | 500 W. Madison Ave Suite 1000 | Chicago, IL 60661 Office: 312-894-6964 | Mobile: 773-850-9679 | Facsimile: 312-894-5001 This message is intended only for the use of the Addressee and may contain information that is PRIVATE and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify the sender immediately. On 10/1/13 4:31 PM, "Paul Eggert" <eggert(a)cs.ucla.edu> wrote: >The 2013g release of the tz code and data is available. It reflects >the following changes, which were either circulated on the tz mailing >list or are relatively minor technical or administrative changes: > > Changes affecting current and near-future time stamps > > Morocco now observes DST from the last Sunday in March to the last > Sunday in October, not April to September respectively. (Thanks > to Steffen Thorsen.) > > Changes affecting 'zic' > > 'zic' now runs on platforms that lack both hard links and symlinks. > (Thanks to Theo Veenker for reporting the problem, for MinGW.) > Also, fix some bugs on platforms that lack hard links but have >symlinks. > > 'zic -v' again warns that Asia/Tehran has no POSIX environment >variable > to predict the far future, fixing a bug introduced in 2013e. > > Changes affecting the build procedure > > The 'leapseconds' file is again put into the tzdata tarball. > Also, 'leapseconds.awk', so tzdata is self-contained. (Thanks to > Matt Burgess and Ian Abbott.) The timestamps of these and other > dependent files in tarballs are adjusted more consistently. > > Changes affecting documentation and commentary > > The README file is now part of the data tarball as well as the code. > It now states that files are public domain unless otherwise specified. > (Thanks to Andrew Main (Zefram) for asking for clarifications.) > Its details about the 1989 release moved to a place of honor near > the end of NEWS. > > >Here are links to the release files: > > ftp://ftp.iana.org/tz/releases/tzcode2013g.tar.gz > ftp://ftp.iana.org/tz/releases/tzdata2013g.tar.gz > >The files are also available via HTTP as follows: > > http://www.iana.org/time-zones/repository/releases/tzcode2013g.tar.gz > http://www.iana.org/time-zones/repository/releases/tzdata2013g.tar.gz > >Each release file has a GPG signature, which can be retrieved by >appending ".asc" to the above URLs. Copies of these signatures are >appended to this message. > >As usual, links to the latest release files are here: > > http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz > http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz > > ftp://ftp.iana.org/tz/tzcode-latest.tar.gz > ftp://ftp.iana.org/tz/tzdata-latest.tar.gz > >This release corresponds to commit >320239cf816c3ea27583867d195085df58a29899 >dated Mon Sep 30 21:08:26 2013 -0700 and tagged 2013g >in the unofficial github repository at <https://github.com/eggert/tz>. > >Here are the GPG checksums for the release files: > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.12 (GNU/Linux) > >iQIcBAABAgAGBQJSSkvxAAoJEO2X6Q5iqn40/IIQAKPy09y3OspqzMTHyEgjqMjF >8cIC6DtLPsyPmSqynfDJcyt315UNAB+16YLwAhQ2YwLjNR7OHuFMODcxe8cC3uuG >q7S343EjXrlpPoEEtzeecn+vQxlmg0IfR1nuHcQnL3I9VJjLNHG2oq9iEzGzS/VR >WRFOSLyn3miBF7LuB3GVWm8L/gFneK9O6odIdRYRiD1uZobgxG+RH/QwHwZC2Cqt >h4G42jv9scE8RU/pME9MKOYRdUMlH16rmtSpqbGdcZFeqnN9d5WpnzvUbDZ49GNg >cozDv0zMfDoVTMhqMidRj7j9+CeH0jjTiAwb6yGS0JHRlAHkOAxtU5O45hzjqAFf >jaAPHBvUK26NkkmdR31U0pTLF2o79VRw70n8WpxaoG9RdaJc1e8we83gvr9h7z+j >lBQVblWpwCItUCNlTcRtn2QHwy3i7WNJtnw4wmJZSqn7s+gOdiICMVU0ALe8Whe1 >W2HUmAMyulK6iPyhdXKNrrpIr3WsGDS+R6VieJptWtjLOeSDpXKgjNNDmpDjg0u1 >tpnB36W4eZk2c22xGkI/dggvgjvI4mMzID2t029+rhebQHZ6VmzqM+SRK0KhvZtf >wFMH5ZqUEV5uKHFMZmVp7cAmVcRlWpGykE+2LRY0LPSpk5G3WEsHMP3Gv1i1EmI6 >jdfLGvhsWTUlPWyFOP8d >=W0k0 >-----END PGP SIGNATURE----- >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.12 (GNU/Linux) > >iQIcBAABAgAGBQJSSkvxAAoJEO2X6Q5iqn40KkYQAKD9qGaNIS1npFQFfbMj2Z8/ >LzJV1DEy3SRnR+IhOPWhnOkarbirlKIm1MTEbOX2WwPuM0oSPoCVfBLdQqdnjhnQ >sc4dhmtUIp/i3EJYTsDgim8CsZ/DDJCLL1qxCi+MsjizuZqcpj7V/qivRmTGPdsY >Z9jBgHdq7CCOxTx6Sv+P2Bv2oz9LxD4w9dXIeeN04R/f7u12Yc1zedDayn9qqHYz >EOotuxanSybxb25uKWm8EawA+zOcaVhkO1NzIG3YVJKLJCMxE2NGzt8rH3b1e6gn >Ql+G4h3J/eTX507VDa2aODEqezyUw+ObMNl/eS/DqBdlPCAn5qI9/aIu4NaRT1wX >XCU7UDyQ4smC7ugYqju5+THTokAc7fLKz79req6yesGmw5Y7nm94CwNhSVA1Fky5 >wUEZGX7lrVU967cb4IqQGhRz+DeglKROZw3WDwL2uNuIBEuICkWNYZ232ikEMtVa >QGwS3Q5XtqghV9ZQy8IbhA9LmJ76LMbRGbNjl30bmM1RDju3qgcKNSqDuapTxLXn >UgQ5PDbwLtIrgZ+OAJFvLfivgyVElgo9l2qg+RtNytz9Zqy/Fdh/hq+z/u70sY0y >HXUBQ3Gl/ZjZ4juYe7zZbkQPKeYNQ9HK9miKHM0SdYrI12+KGthR6wHqaCSKZUGd >32DdW5wvGERZC+Qn739c >=oMLZ >-----END PGP SIGNATURE----- > >_______________________________________________ >tz-announce mailing list >tz-announce(a)iana.org >https://mm.icann.org/mailman/listinfo/tz-announce

1 0

tzcode2013g and tzdata2013g available
by Paul Eggert Oct. 1, 2013

Oct. 1, 2013

[This is a copy of a message that just got sent to tz-announce(a)iana.org; it didn't get propagated automatically to tz(a)iana.org so I'm rebroadcasting it by hand.] The 2013g release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Changes affecting current and near-future time stamps Morocco now observes DST from the last Sunday in March to the last Sunday in October, not April to September respectively. (Thanks to Steffen Thorsen.) Changes affecting 'zic' 'zic' now runs on platforms that lack both hard links and symlinks. (Thanks to Theo Veenker for reporting the problem, for MinGW.) Also, fix some bugs on platforms that lack hard links but have symlinks. 'zic -v' again warns that Asia/Tehran has no POSIX environment variable to predict the far future, fixing a bug introduced in 2013e. Changes affecting the build procedure The 'leapseconds' file is again put into the tzdata tarball. Also, 'leapseconds.awk', so tzdata is self-contained. (Thanks to Matt Burgess and Ian Abbott.) The timestamps of these and other dependent files in tarballs are adjusted more consistently. Changes affecting documentation and commentary The README file is now part of the data tarball as well as the code. It now states that files are public domain unless otherwise specified. (Thanks to Andrew Main (Zefram) for asking for clarifications.) Its details about the 1989 release moved to a place of honor near the end of NEWS. Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2013g.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2013g.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2013g.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2013g.tar.gz Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz This release corresponds to commit 320239cf816c3ea27583867d195085df58a29899 dated Mon Sep 30 21:08:26 2013 -0700 and tagged 2013g in the unofficial github repository at <https://github.com/eggert/tz>. Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJSSkvxAAoJEO2X6Q5iqn40/IIQAKPy09y3OspqzMTHyEgjqMjF 8cIC6DtLPsyPmSqynfDJcyt315UNAB+16YLwAhQ2YwLjNR7OHuFMODcxe8cC3uuG q7S343EjXrlpPoEEtzeecn+vQxlmg0IfR1nuHcQnL3I9VJjLNHG2oq9iEzGzS/VR WRFOSLyn3miBF7LuB3GVWm8L/gFneK9O6odIdRYRiD1uZobgxG+RH/QwHwZC2Cqt h4G42jv9scE8RU/pME9MKOYRdUMlH16rmtSpqbGdcZFeqnN9d5WpnzvUbDZ49GNg cozDv0zMfDoVTMhqMidRj7j9+CeH0jjTiAwb6yGS0JHRlAHkOAxtU5O45hzjqAFf jaAPHBvUK26NkkmdR31U0pTLF2o79VRw70n8WpxaoG9RdaJc1e8we83gvr9h7z+j lBQVblWpwCItUCNlTcRtn2QHwy3i7WNJtnw4wmJZSqn7s+gOdiICMVU0ALe8Whe1 W2HUmAMyulK6iPyhdXKNrrpIr3WsGDS+R6VieJptWtjLOeSDpXKgjNNDmpDjg0u1 tpnB36W4eZk2c22xGkI/dggvgjvI4mMzID2t029+rhebQHZ6VmzqM+SRK0KhvZtf wFMH5ZqUEV5uKHFMZmVp7cAmVcRlWpGykE+2LRY0LPSpk5G3WEsHMP3Gv1i1EmI6 jdfLGvhsWTUlPWyFOP8d =W0k0 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJSSkvxAAoJEO2X6Q5iqn40KkYQAKD9qGaNIS1npFQFfbMj2Z8/ LzJV1DEy3SRnR+IhOPWhnOkarbirlKIm1MTEbOX2WwPuM0oSPoCVfBLdQqdnjhnQ sc4dhmtUIp/i3EJYTsDgim8CsZ/DDJCLL1qxCi+MsjizuZqcpj7V/qivRmTGPdsY Z9jBgHdq7CCOxTx6Sv+P2Bv2oz9LxD4w9dXIeeN04R/f7u12Yc1zedDayn9qqHYz EOotuxanSybxb25uKWm8EawA+zOcaVhkO1NzIG3YVJKLJCMxE2NGzt8rH3b1e6gn Ql+G4h3J/eTX507VDa2aODEqezyUw+ObMNl/eS/DqBdlPCAn5qI9/aIu4NaRT1wX XCU7UDyQ4smC7ugYqju5+THTokAc7fLKz79req6yesGmw5Y7nm94CwNhSVA1Fky5 wUEZGX7lrVU967cb4IqQGhRz+DeglKROZw3WDwL2uNuIBEuICkWNYZ232ikEMtVa QGwS3Q5XtqghV9ZQy8IbhA9LmJ76LMbRGbNjl30bmM1RDju3qgcKNSqDuapTxLXn UgQ5PDbwLtIrgZ+OAJFvLfivgyVElgo9l2qg+RtNytz9Zqy/Fdh/hq+z/u70sY0y HXUBQ3Gl/ZjZ4juYe7zZbkQPKeYNQ9HK9miKHM0SdYrI12+KGthR6wHqaCSKZUGd 32DdW5wvGERZC+Qn739c =oMLZ -----END PGP SIGNATURE-----

1 0

Our Palestinian New Time Zone
by Fadia Al Marei Oct. 1, 2013

Oct. 1, 2013

Dear All Our country Palestine do not have an official TIME Zone , we need to know what is the needed information and official documents from our side to have our TIME Zone which could be published to all companies we are dealing with (Microsoft, Redhat Linux , SUSE Linux , SUN , HP , CISCO and others ) ,we need detailed information if you please. BR; [Description: Description: Description: Description: Logo2] Fadia Almarei-Jarrar | Data Center Infrastructure Team Leader - Data Center Department Fax:+970-2-241111 | Tel:+970-2-2410077 | Mobile:+970-59-8080077| Website: www.Hulul.com<http://www.Hulul.com> [Description: Description: Description: Description: cid:image003.png@01CA04A2.875C8100]Please consider the environment before printing this email[1] ________________________________ [1]Optional

7 9

minor error in NEWS
by Denis Excoffier Sept. 30, 2013

Sept. 30, 2013

Hello, In the NEWS file or the recent modification for Morocco, it can be read: Unreleased, experimental changes + Changes affecting current and near-future time stamps + + Morocco changed their rules, and now falls back the first Sunday + in October, not September. (Thanks to Steffen Thorsen.) + Changes affecting 'zic' Should be "the last Sunday in October". Regards, Denis Excoffier.

1 0

Morocco TimeZone Update rules
by Hicham Aoufir Sept. 29, 2013

Sept. 29, 2013

Hello, The Moroccan governement has approved a decision that maintain the summer time one more month until last sunday of October of each year. http://www.maroc.ma/fr/actualites/lhoraire-dete-gmt1-maintenu-jusquau-27-oc… -- Cordialement / Kind Regards / مع أطيب التحيات * * *AOUFIR Hicham* Ingénieur en Systèmes d'Information Admnistrateur Systèmes Unix/Linux (+212)644158121

1 0

Spain is considering time zone change
by Alexander Krivenyshev Sept. 28, 2013

Sept. 28, 2013

According to some news, Spain is considering time zone change: Spanish MPs considering time zone change http://topnews.es/content/2829-spanish-mps-considering-time-zone-change Spain could put clocks back to boost economy http://www.thelocal.es/20130927/spain-could-put-clocks-back-to-boost-economy or http://www.worldtimezone.com/dst_news/dst_news_spain01.html Alexander Krivenyshev, http://www.WorldTimeZone.com

1 0

global 'timezone' on x32
by enh Sept. 27, 2013

Sept. 27, 2013

localtime.c defines 'timezone' as a time_t. glibc (which doesn't use tzcode) and bionic (which does) currently declare 'timezone' as a long int. POSIX also says 'long'. the mismatch causes trouble on x32. --elliott

2 2

leapseconds.awk missing from data tarball?
by Matt Burgess Sept. 26, 2013

Sept. 26, 2013

Hi, I note from the recent release notes that the leap-seconds.list file is generated using leapseconds.awk. Previous to this change, it was possible to compile and install the tz files just using the tzdata tarball. As the leapseconds.awk file is only shipped in the tzcode tarball, this is now no longer possible. Would it be possible to ship either the leapseconds.awk file, or a generated copy of leap-seconds.list in the tzdata tarball so that the tzcode tarball is once more no longer required? Thanks, Matt.

4 5

tzcode2013f and tzdata2013f available
by Paul Eggert Sept. 26, 2013

Sept. 26, 2013

The 2013f release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor administrative changes: Changes affecting near-future time stamps Tocantins will very likely not observe DST starting this spring. (Thanks to Steffen Thorsen.) Jordan will likely stay at UTC+3 indefinitely, and will not fall back this fall. Palestine will fall back at 00:00, not 01:00. (Thanks to Steffen Thorsen.) Changes affecting API The types of the global variables 'timezone' and 'altzone' (if present) have been changed back to 'long'. This is required for 'timezone' by POSIX, and for 'altzone' by common practice, e.g., Solaris 11. These variables were originally 'long' in the tz code, but were mistakenly changed to 'time_t' in 1987; nobody reported the incompatibility until now. The difference matters on x32, where 'long' is 32 bits and 'time_t' is 64. (Thanks to Elliott Hughes.) Changes affecting the build procedure Avoid long strings in leapseconds.awk to work around a mawk bug. (Thanks to Cyril Baurand.) Changes affecting documentation and commentary New file 'NEWS' that contains release notes like this one. Paraguay's law does not specify DST transition time; 00:00 is customary. (Thanks to Waldemar Villamayor-Venialbo.) Minor capitalization fixes. Changes affecting version-control only The experimental github repository now contains annotated and signed tags for recent releases, e.g., '2013e' for Release 2013e. Releases are tagged starting with 2012e; earlier releases were done differently, and tags would either not have a simple name or not exactly match what was released. 'make set-timestamps' is now simpler and a bit more portable. Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2013f.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2013f.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2013f.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2013f.tar.gz Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz This release corresponds to commit 7436d7438735104103d6d6b0ae5b45bdef7b69a2 dated Tue Sep 24 23:37:36 2013 -0700 in the unofficial github repository at <https://github.com/eggert/tz>. Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJSQoY1AAoJEO2X6Q5iqn40MOwP/j4xZCapf6Wqzmr7aexvNAVj t+L665BgXBYgmh3V+D1B1mj+B1Ilu0+3z0b4xyNB938trMuWMoBVfBjYfw+nQgbk hoIFggl3jh4BmCJqL7gLRYDBMxhuTcZfDbLHYJ1znuNC63PJej8X3uOXBR1TUQC4 /D40tArmDrpA2KQ5uBbBnIqWFmWUqbPPM+4Zb02TFI6ElIzN9yF7hO8c4AzevYZG SuY6DzdRAvt+HKkPb5BSH5qIb9WnOHPHlh1gb8Ek8IjfC0Y/NPFkfivBcRLcvU3D BMH+ysfhrt/L2shGbN9xJY72hflWZAlBUveggtEEem4ZGyR3jt494qs5bAmfFs5c NEl4FOJ7A0zR4zOOXasY8d8H9x8QHACM7pnFl007CC3/X65ahMDYznug3m0fIlTT FIVExwC7vu5q9phKZqllsf1WDDlYsRDSjvZRyJftAo8d7uiX/hSRV62ENzvDpZTE IhKbQcJO4o3HSy1ZAR/8ZBOZZTrfuCTVia3HQSv+z9HE1DcqZr24Vc5rUxOWlLAG Ikd+F23YtPqH7d+PVZMBDIZkqeu7qB/3a7WSzEvE/eYIKeoGojQBIvz9swZd5vmb tbHrYmvCM9nuPat6XfMhCms80gjcxPSqS3+UODvq01+OOG/v+1uxBavxZWjMo/6n yoay8oUjHbaBUSy9gjv/ =mvcv -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJSQoY1AAoJEO2X6Q5iqn40MHYP/Aq8zW+aeJkn0MP55pJYL/oJ 7yGojddjV7FApzoqiBnTqsmUtxMWdrQR8ZAejSoKvZWWI/XwhHv6nPO6ZAlMB7WV 1lakGSjGD055ZhOQaViMF0/i2iQJXrWW+YAy0QWUhJSSLOHZ/Mk0dUVPb2I/3XPW uFuR8xmrJE4gBTEXyN9CL/ebmpvV0lEUbNEj46Y/SKDDqcF8pA1WJlbCiqcxwiTp lS0B/KuwhKof8N3ij7TnIlIM/HzwnTFiL3zabvUNErhRtP3PWggCVanyULnNcSJU 2C4pSQRC3CW2gIPZfF7e3EaV0RoraeinRPdSM+HHsgM13WHw/EuXQ3QJXvJDYoWc w0VnD2cnDqlSBEkWqI/SdK4W3bRhR9lhskFJSBGxSr6XBBXzYAgFu4dzL5DzCSd5 9ITsIC/2FMslLNAEkufNOpHLV7BBrrMDmtwuM2B1yc4zkMXVMKof9v0BxnODGTsH gxncarfm19i7Ew/6rz9UqVH8gsPt2JkMbmLnPjoEo5bgF5JQINO3WC6FtLWxNlPn 5DUfwhE9XcdxoJCl+sA3DsB3qxWz3VHSVH8M3OYSxtRqzRFXpNcLXbwSxz+IlSjp +sTuM8WAECLsSRT5S1zIroobbs2sguY6Gipk9Lq3L4Lux3eHkMzlCoZk36OJdU6K U/ScBctj4rv1sM33kqJW =eD7x -----END PGP SIGNATURE-----

3 2

compiling tzcode with mingw gcc compiler
by Theo Veenker Sept. 26, 2013

Sept. 26, 2013

Dear maintainers of the tzcode, I noticed I could't build the tzcode from Mingw gcc. Therefore I'd like to suggest some additions/changes. They are fairly trivial, see below. Theo Veenker Main change required is the addition of a (conditional) link() function into zic.c as this function is not provided on a Windows platform. private.h: Add: #ifndef HAVE_LINK #define HAVE_LINK 1 #endif /* !defined HAVE_LINK */ zic.c: Add: #if !HAVE_LINK #define SCRATCH_SIZE 8000 int link(const char * fromname, const char * toname) { FILE * fi; FILE * fo; char * scratch; int err = 0; fi = fopen(fromname, "rb"); if (!fi) return -1; fo = fopen(toname, "wb"); if (!fo) { fclose(fi); return -1; } scratch = (char*)emalloc(SCRATCH_SIZE); while (!feof(fi)) { int nread = fread(scratch, 1, SCRATCH_SIZE, fi); if (nread > 0) { int nwritten = fwrite(scratch, 1, nread, fo); if (nwritten != nread) { err = -1; break; } } else if (feof(fi)) { break; } else if (ferror(fi)) { err = -1; break; } } free(scratch); fclose(fo); fclose(fi); return err; } #endif /* !HAVE_LINK */ Makefile: Linking zdump requires asctime.c and asctime.o to be added to symbols TZDSRCS resp. TZDOBJS: TZDSRCS= zdump.c localtime.c asctime.c ialloc.c TZDOBJS= zdump.o localtime.o asctime.o ialloc.o Also add comment: # -DHAVE_LINK=0 if your system lacks the link function To test compilation using i686-w64-mingw32-gcc under Linux: make CFLAGS="-DHAVE_STDINT_H -DSTD_INSPIRED -DHAVE_SYS_WAIT_H=0 -DHAVE_SYS_STAT_H=0 -DHAVE_UNISTD_H=0 -DHAVE_SYMLINK=0 -DHAVE_LINK=0" cc=i686-w64-mingw32-gcc To test compilation using Mingw gcc under Windows: make CFLAGS="-DHAVE_STDINT_H -DSTD_INSPIRED -DHAVE_SYS_WAIT_H=0 -DHAVE_SYS_STAT_H=0 -DHAVE_UNISTD_H=0 -DHAVE_SYMLINK=0 -DHAVE_LINK=0" cc=gcc -- Theo Veenker | Beexy - Behavioral Experiment Software +31(0)524-541531 | +31(0)6-42525777 mobile theo.veenker(a)beexy.nl | www.beexy.nl

2 1

PD notices
by Zefram Sept. 25, 2013

Sept. 25, 2013

I have some code that repackages the tz database, and along the way it checks that the subset that it's repackaging is in the public domain. The check is required because not all of the files are PD (some of the man pages are BSD licensed), and the license statement on the automatically-generated package needs to be correct. The code checks by looking for the notices that are at the top of most of the files. I have found that it quite frequently gets broken by small changes in file formatting, or new files with novel format. 2013e broke it by adding leap-seconds.list, and 2013f has just broken it again by adding NEWS. Can we come up with some consistent formatting rules to make the PD notices machine readable? It doesn't have to be a single structure for all file types, just a limited repertoire that code can reliably apply. Or a separate machine-readable list of files with a single statement that the listed files are all PD. -zefram

3 3

Gaza/West Bank likely to end DST 1 hour earlier
by Steffen Thorsen Sept. 25, 2013

Sept. 25, 2013

The Gaza and West Bank are ending DST Thursday at midnight (2013-09-27 00:00:00) (one hour earlier than last year and current rule in tzdata). This source in English, says "that winter time will go into effect at midnight on Thursday in the West Bank and Gaza Strip": http://english.wafa.ps/index.php?action=detail&id=23246 and also mentions it here: http://english.wafa.ps/index.php?action=detail&id=23254 The official source and this other source in Arabic, with Google Translate translates to "Friday night", we assume this English source was based on this government source, and that midnight between Thursday and Friday is correct: http://www.palestinecabinet.gov.ps/ar/Views/ViewDetails.aspx?pid=1252 http://felesteen.ps/details/news/100581/%D8%A8%D8%AF%D8%A1-%D8%A7%D9%84%D8%… Best regards, Steffen Thorsen - timeanddate.com

3 2

America/Montreal has been Removed in the zone.tab file for 2013e?
by Richard Andersen (TT) Sept. 24, 2013

Sept. 24, 2013

Hi, I have noticed that “America/Montreal” entry was removed from the zone.tab file in the 2013e release. I am not sure if this is a mistake, but I wanted someone to know… Thanks!

2 1

tzcode2013e and tzdata2013e available
by Paul Eggert Sept. 24, 2013

Sept. 24, 2013

The 2013e release of the tz code and data is available. It reflects the following changes circulated on the tz mailing list: Changes affecting near-future time stamps This year Fiji will start DST on October 27, not October 20. (Thanks to David Wheeler for the heads-up.) For now, guess that Fiji will continue to spring forward the Sunday before the fourth Monday in October. Changes affecting current and future time zone abbreviations Use WIB/WITA/WIT rather than WIT/CIT/EIT for alphabetic Indonesian time zone abbreviations since 1932. (Thanks to George Ziegler, Priyadi Iman Nurcahyo, Zakaria, Jason Grimes, Martin Pitt, and Benny Lin.) This affects Asia/Dili, Asia/Jakarta, Asia/Jayapura, Asia/Makassar, and Asia/Pontianak. Use ART (UTC-3, standard time), rather than WARST (also UTC-3, but daylight saving time) for San Luis, Argentina since 2009. Changes affecting Godthab time stamps after 2037 if version mismatch Allow POSIX-like TZ strings where the transition time's hour can range from -167 through 167, instead of the POSIX-required 0 through 24. E.g., TZ='FJT-12FJST,M10.3.1/146,M1.3.4/75' for the new Fiji rules. This is a more-compact way to represent far-future time stamps for America/Godthab, America/Santiago, Antarctica/Palmer, Asia/Gaza, Asia/Hebron, Asia/Jerusalem, Pacific/Easter, and Pacific/Fiji. Other zones are unaffected by this change. (Derived from a suggestion by Arthur David Olson.) Allow POSIX-like TZ strings where daylight saving time is in effect all year. E.g., TZ='WART4WARST,J1/0,J365/25' for Western Argentina Summer Time all year. This supports a more-compact way to represent the 2013d data for America/Argentina/San_Luis. Because of the change for San Luis noted above this change does not affect the current data. (Thanks to Andrew Main (Zefram) for suggestions that improved this change.) Where these two TZ changes take effect, there is a minor extension to the tz file format in that it allows new values for the embedded TZ-format string, and the tz file format version number has therefore been increased from 2 to 3 as a precaution. Version-2-based client code should continue to work as before for all time stamps before 2038. Existing version-2-based client code (tzcode, GNU/Linux, Solaris) has been tested on version-3-format files, and typically works in practice even for time stamps after 2037; the only known exception is America/Godthab. Changes affecting time stamps before 1970 Pacific/Johnston is now a link to Pacific/Honolulu. This corrects some errors before 1947. Some zones have been turned into links, when they differ from existing zones only in older data that was likely invented or that differs only in LMT or transition from LMT. These changes affect only time stamps before 1943. The affected zones are: Africa/Juba, America/Anguilla, America/Aruba, America/Dominica, America/Grenada, America/Guadeloupe, America/Marigot, America/Montserrat, America/St_Barthelemy, America/St_Kitts, America/St_Lucia, America/St_Thomas, America/St_Vincent, America/Tortola, and Europe/Vaduz. (Thanks to Alois Treindl for confirming that the old Europe/Vaduz zone was wrong and the new link is better for WWII-era times.) Change Kingston Mean Time from -5:07:12 to -5:07:11. This affects America/Cayman, America/Jamaica and America/Grand_Turk time stamps from 1890 to 1912. Change the UT offset of Bern Mean Time from 0:29:44 to 0:29:46. This affects Europe/Zurich time stamps from 1853 to 1894. (Thanks to Alois Treindl). Change the date of the circa-1850 Zurich transition from 1849-09-12 to 1853-07-16, overriding Shanks with data from Messerli about postal and telegraph time in Switzerland. Changes affecting time zone abbreviations before 1970 For Asia/Jakarta, use BMT (not JMT) for mean time from 1923 to 1932, as Jakarta was called Batavia back then. Changes affecting API The 'zic' command now outputs a dummy transition when far-future data can't be summarized using a TZ string, and uses a 402-year window rather than a 400-year window. For the current data, this affects only the Asia/Tehran file. It does not affect any of the time stamps that this file represents, so zdump outputs the same information as before. (Thanks to Andrew Main (Zefram).) The 'date' command has a new '-r' option, which lets you specify the integer time to display, a la FreeBSD. The 'tzselect' command has two new options '-c' and '-n', which lets you select a zone based on latitude and longitude. The 'zic' command's '-v' option now warns about constructs that require the new version-3 binary file format. (Thanks to Arthur David Olson for the suggestion.) Support for floating-point time_t has been removed. It was always dicey, and POSIX no longer requires it. (Thanks to Eric Blake for suggesting to the POSIX committee to remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy Heninger, Arthur David Olson, and Alois Treindl, for reporting bugs and elucidating some of the corners of the old floating-point implementation.) The signatures of 'offtime', 'timeoff', and 'gtime' have been changed back to the old practice of using 'long' to represent UT offsets. This had been inadvertently and mistakenly changed to 'int_fast32_t'. (Thanks to Christos Zoulos.) The code avoids undefined behavior on integer overflow in some more places, including gmtime, localtime, mktime and zdump. Changes affecting the zdump utility zdump now outputs "UT" when referring to Universal Time, not "UTC". "UTC" does not make sense for time stamps that predate the introduction of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen for clarifying UT vs UTC.) Data changes affecting behavior of tzselect and similar programs Country code BQ is now called the more-common name "Caribbean Netherlands" rather than the more-official "Bonaire, St Eustatius & Saba". Remove from zone.tab the names America/Montreal, America/Shiprock, and Antarctica/South_Pole, as they are equivalent to existing same-country-code zones for post-1970 time stamps. The data for these names are unchanged, so the names continue to work as before. Changes affecting code internals zic -c now runs way faster on 64-bit hosts when given large numbers. zic now uses vfprintf to avoid allocating and freeing some memory. tzselect now computes the list of continents from the data, rather than have it hard-coded. Minor changes pacify GCC 4.7.3 and GCC 4.8.1. Changes affecting the build procedure The 'leapseconds' file is now generated automatically from a new file 'leap-seconds.list', which is a copy of <ftp://time.nist.gov/pub/leap-seconds.list>. A new source file 'leapseconds.awk' implements this. The goal is simplification of the future maintenance of 'leapseconds'. When building the 'posix' or 'right' subdirectories, if the subdirectory would be a copy of the default subdirectory, it is now made a symbolic link if that is supported. This saves about 2 MB of file system space. The links America/Shiprock and Antarctica/South_Pole have been moved to the 'backward' file. This affects only nondefault builds that omit 'backward'. Changes affecting version-control only .gitignore now ignores 'date'. Changes affecting documentation and commentary Changes to the 'tzfile' man page It now mentions that the binary file format may be extended in future versions by appending data. It now refers to the 'zdump' and 'zic' man pages. Changes to the 'zic' man page It lists conditions that elicit a warning with '-v'. It says that the behavior is unspecified when duplicate names are given, or if the source of one link is the target of another. Its examples are updated to match the latest data. The definition of white space has been clarified slightly. (Thanks to Michael Deckers.) Changes to the 'Theory' file There is a new section about the accuracy of the tz database, describing the many ways that errors can creep in, and explaining why so many of the pre-1970 time stamps are wrong or misleading (thanks to Steve Allen, Lester Caine, and Garrett Wollman for discussions that contributed to this). The 'Theory' file describes LMT better (this follows a suggestion by Guy Harris). It refers to the 2013 edition of POSIX rather than the 2004 edition. It's mentioned that excluding 'backward' should not affect the other data, and it suggests at least one zone.tab name per inhabited country (thanks to Stephen Colebourne). Some longstanding restrictions on names are documented, e.g., 'America/New_York' precludes 'America/New_York/Bronx'. It gives more reasons for the 1970 cutoff. It now mentions which time_t variants are supported, such as signed integer time_t. (Thanks to Paul Goyette for reporting typos in an experimental version of this change.) (Thanks to Philip Newton for correcting typos in these changes.) Documentation and commentary is more careful to distinguish UT in general from UTC in particular. (Thanks to Steve Allen.) Add a better source for the Zurich 1894 transition. (Thanks to Pierre-Yves Berger.) Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2013e.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2013e.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2013e.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2013e.tar.gz Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz This release corresponds to commit db6270a00d1a364865f3080ac41d8d6d42f5c833 dated Thu Sep 19 23:50:04 2013 -0700 in the unofficial github repository at <https://github.com/eggert/tz>. Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJSO/DcAAoJEO2X6Q5iqn40rbIQAJcRAifvpdyKii++x7uB3JEd zYLCM9U2AkQXySjr6f4LYyPM7gEj9VvXRI4Ux3ZZ1tfxKW4dIJwjGjqjPIug/zmz khc0yJvrlUukCd9rDQZR+LRHNLPeUsSaSnC/5iM8UuzYIV4PYJLyI1+yob/4X6wq 9ompg+Fm/0jNHIh35ICq5QsCdIBMJxAN2QMwp5v3cbcmOKQQHrrGW89K4jlkzfL5 GGm+oWaodSSTIprPi7qBzGFk4G84aXqKl7Da2cXKzcVd70jvmoHWEiy2J0qdqhh8 N6GxJJ6X9mtj+Cuau9mmiBmtxynANcSKVbVFLUmIOroCl2V9RYhyDmjzd0Nk7oew v5ZGH1sTjFjPZ4bACYENLOZLVW4K32cpH8DBG47gnj9yhU5iDdAn/TwixMrZ6dSE m2xNuK9aLMCzoS6dFJJMHut0ojeuqq2zuDR4OmSsh2fZDBgBWcKVDdAcNNdDdD2G 5/aoWR1FPxYApkOhGlnsAZzuugxJbVA69kcWTDy/UoIui1Ozv3i8OabcUjvoU0fD +umoLz7LaWFdgKT7RW17fkxIpUpikYdLxx/cBQ9mnl9BsBid+BhO2V+UEDt1w1nv CG5qgjmcpFdTyzMXyDJ2c0snLh2X416+tOqOq3n8vJDlU35bPLlTVyQ4wGhZKOSn PzbV+Idmr7mbTdECKs4h =QOEp -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJSO/DnAAoJEO2X6Q5iqn40IeYP/Rgv723SYqXyKxcdJ3uRKDVI KciMh2X0OZqEyOiS9Vq2m7Fvt/Xp+H++NWyvTimBI+vhbiHHM92x3r27qvTqPmED T2+S4vcCnIXkXGODcqyum8pY2HO0oJC6VJ+/7WnJ7U/9zWHDq/cENuQ4SnulY+dS 9b/tcUePWRHJmMBB+SqQD8yFclH8C1LN5VRbh+6wAq5rgG23+Bzqe2cq1OXKxNc7 Z0i5JfMSSIEW6qIHjKLDIdygx7upSRjP2K+xYPjyTzszxmUZ0FEZhV9ZG2/6eNJe sHXg0aXCTL3dgd1h91hQiN8CNLLv3JNx7livFD+OTTgPyh3AqE2yHBODjLg0OzYG zFXryq1/bsFvJDqtDGs1BlBQYDuklaYpaCOOcbXnZMRwrgg8mD533qirSwr5Jxb3 XZtoG0u+yFOXb7N/ARcUVjbAG1ypfKFV4CZ1BlDbXlQNmr/5Cqpw5igAgjmuV+Ol E8ZpYXB3X9eJxfNhVLtjXWTfSoQfvMi2RNG2iv0x8/PdqLFnO2mxy8PwI3JkuJX/ Y2zJzZCIIjJCkAinzJy45WUJGDNVnicUViJ+W9TStfKXhxvidiXGmQdh3TsyH5Kx bdg3ZVHkWT19T5Pl/+7Rfqn5YO11/V3RvwGLD1mznRqhXJhosi/mp2dQCTRqqw3A sl/rxtJJWY8fy6sCc052 =kyxK -----END PGP SIGNATURE-----

4 4

McMurdo/South Pole
by Stephen Colebourne Sept. 23, 2013

Sept. 23, 2013

Since McMurdo was not founded until 16 Feb 1956 (wikipedia), I think that it is simply incorrect data to assign any time-zone transitions until that date. There simply were no DST transitions in McMurdo in the 1930s as it did not exist. https://github.com/jodastephen/tzdiff/commit/57aac13605f184a46f74d22f7dddc9… This is a a case where an ID that has existed for a long time with reasonably good data that has now been degraded through a Zone to Link conversion. Stephen (I hadn't realised the extent of the data pollution of McMurdo until I did my recent data analysis)

8 24

Deep Impact: worng time zone?
by Arthur David Olson Sept. 23, 2013

Sept. 23, 2013

"...analysis has uncovered a potential problem with computer time tagging..." "NASA's Deep Space Comet Hunter Mission Comes to an End" http://www.jpl.nasa.gov/news/news.php?release=2013-287 --ado

4 3

A New Rule? (was McMurdo/South Pole)
by Bill Seymour Sept. 22, 2013

Sept. 22, 2013

A partly-baked idea to solve the more general problem of when zones appear and disappear: would it make sense to have another kind of entry in the zone RULES column to indicate that we should now follow another zone's practice? How about the keyword, Zone, a space, and the name of the other zone, with the next column following whitespace, if present, being the [UNTIL] column?

2 4

Re: [tz] draft of change summary for next tz release
by David Patte ₯ Sept. 21, 2013

Sept. 21, 2013

And some of us prefer having at least one zone for each ISO 3166-1 country. Several of us understood the old theory file to require this. 1970 is an arbitrary computer geek cutoff point, with not much meaning to general time zone history.

13 41

Jordan permanently on UTC+3?
by Paul Eggert Sept. 20, 2013

Sept. 20, 2013

I looked for hints about what Jordan's going to do with its clocks next month, and found this article from February: Cancelling winter saved Jordan $7 million Petra News Agency 2013-02-20 11:34 UTC http://www.albawaba.com/business/jordan-winter-electricity--472005 Currently the tz database is guessing that Jordan will revert to UTC+2 next month, but if this article is any indication they'll stay at UTC+3 indefinitely, which means the obvious tz patch (already mentioned in the 2012-10-15 comments) would be appropriate.

1 0

Tocantins in Brazil probably not observing DST this season
by Steffen Thorsen Sept. 20, 2013

Sept. 20, 2013

According to this article, Tocantins in Brazil is very likely not to observe DST from October. The decree has not yet been issued, so the decision may still be revoked, but we assume it is very likely because it has been announced by the congressman and DST is so unpopular there. http://conexaoto.com.br/2013/09/18/ministerio-confirma-que-tocantins-esta-f… We will keep this article updated when this is confirmed: http://www.timeanddate.com/news/time/brazil-starts-dst-2013.html Best regards, Steffen Thorsen - timeanddate.com

2 1

Getting close to new release: testing, testing, ...
by Paul Eggert Sept. 20, 2013

Sept. 20, 2013

We need to release a new version soon, because of Fiji. I did further testing and it appears that the recent changes to add meta-information to the zic output won't fly, because they're incompatible with the GNU C library on Ubuntu 12.04. So we need to rethink that feature. There's no rush to introduce it, so let's omit it from the next release. Also, the -t option recently added to tzselect seems like it will be superseded by the tzwinnow approach, whenever we get that working and stable, so for now I think I'd rather omit this. There are a few other problems found by "make public", mostly links that were in the wrong files. I'll post proposed changes soon. If other people could do some testing that'd be nice. You can run "make public". The output should contain the following diagnostics: warning: "antarctica", line 318: Antarctica/Palmer: pre-2013 clients may mishandle distant timestamps warning: "asia", line 1412: 24:00 not handled by pre-1998 versions of zic warning: "asia", line 2332: 24:00 not handled by pre-1998 versions of zic warning: "asia", line 1026: Asia/Jerusalem: pre-2013 clients may mishandle distant timestamps (rule from "asia", line 1021) warning: "asia", line 1315: Asia/Amman: pre-1994 clients may mishandle distant timestamps warning: "asia", line 2016: Asia/Gaza: pre-2013 clients may mishandle distant timestamps warning: "asia", line 2347: Asia/Hebron: pre-2013 clients may mishandle distant timestamps warning: "australasia", line 269: Pacific/Fiji: pre-2013 clients may mishandle distant timestamps warning: "europe", line 998: America/Godthab: pre-2013 clients may mishandle distant timestamps warning: "southamerica", line 1141: America/Santiago: pre-2013 clients may mishandle distant timestamps warning: "southamerica", line 1313: Pacific/Easter: pre-2013 clients may mishandle distant timestamps along with a very long section that starts as follows, which shows that the tz code is still broken on platforms with unsigned 32-bit time_t (this is a longstanding problem). checking uint32_t zones ... --- tzpublic/int64_t.out 2013-09-11 02:43:50.871343089 -0700 +++ tzpublic/uint32_t.out 2013-09-11 02:43:55.907343185 -0700 @@ -210,278 +210,6 @@ Europe/Andorra Sun Mar 29 01:00:00 2037 UT = Sun Mar 29 03:00:00 2037 CEST isdst=1 Europe/Andorra Sun Oct 25 00:59:59 2037 UT = Sun Oct 25 02:59:59 2037 CEST isdst=1 Europe/Andorra Sun Oct 25 01:00:00 2037 UT = Sun Oct 25 02:00:00 2037 CET isdst=0 -Europe/Andorra Sun Mar 28 00:59:59 2038 UT = Sun Mar 28 01:59:59 2038 CET isdst=0 -Europe/Andorra Sun Mar 28 01:00:00 2038 UT = Sun Mar 28 03:00:00 2038 CEST isdst=1 -Europe/Andorra Sun Oct 31 00:59:59 2038 UT = Sun Oct 31 02:59:59 2038 CEST isdst=1

22 69

Historical data
by David Braverman Sept. 20, 2013

Sept. 20, 2013

I've followed the discussions about historical data with interest. I would like to keep historical data in the tzdb, and I understand why I'm in the minority. But I wonder if there couldn't be a compromise? We've implemented a .NET library that uses the tzdb by interpreting[1] the database rather than by compiling it. So for us, we only deploy the tzdb text files that the customer cares about. Some customers are strictly North American concerns, so we only put the northamerica file in their configuration; others need the whole database of 500-some zones. I think other posters have suggested separating pre-1970 data out into a separate file or file set. This would be perfect for our implementation. For the zic implementation, it seems like compilation is an all-or-nothing deal right now. But would it be difficult to create a build script that includes the historical data to the zic package if someone needs it, in addition to the post-1970 build script? Sorry if the question seems naïve. I just think there's room to compromise here. David Braverman Inner Drive Technology Chicago [1] The tzdb files actually get compiled down to an intermediate set of objects at application start, then live on in a singleton. The process takes about a second on an Azure Extra-Small instance. More info here: https://www.inner-drive.com/Demo/Timezones.aspx

2 1

Data changes for v2013e
by Stephen Colebourne Sept. 20, 2013

Sept. 20, 2013

To better help everyone understand the data changes in 2013e, I've run a tool to analyse them and produce nice coloured git diffs. Changes from 2013d to 2013e https://github.com/jodastephen/tzdiff/commit/57aac13605f184a46f74d22f7dddc9… Lines in green are new added data, lines in red are deletions. >From a purely data perspective, the majority of 2013e changes are LMT based. The largest change is to McMurdo/South_Pole. Previous changes for reference: Changes from 2013c to 2013d https://github.com/jodastephen/tzdiff/commit/db93687fe0d5a6bb4a8ee9dd2d81e9… Changes from 2013b to 2013c https://github.com/jodastephen/tzdiff/commit/d145f2ae94c0587aba378920b44227… Changes from 2013a to 2013b https://github.com/jodastephen/tzdiff/commit/639b044db3e3c24d98b0cf5a6fba85… Stephen

1 0

While searching for Vaduz info...
by Andrew Paprocki Sept. 19, 2013

Sept. 19, 2013

I was hunting around for information when the Vaduz change was proposed and while I didn't find anything related to Vaduz specifically, I came across these very nice historical German documents that may be of use to others. The first from a watch-makers journal in 1916 with many pages discussing the adoption of "summer time" that year and reservations about it. There are mentions of those who proposed the legislation, etc. for anyone who can read German and feels like digging through the various pages talking about it. This is the most relevant page (but there are many others -- search for Sommerzeit): (Page 131) http://babel.hathitrust.org/cgi/pt?id=nyp.33433090896915;view=1up;seq=145 The second discusses WET / CET in terms of railroads and contains an interesting snippet regarding CET being authorized since 1 Feb 1920 as well as Netherlands being 20 minutes offset from GMT. I can't find mention of 1 Feb 1920 in the database, so I'm not sure what it is referring to or if this is new/known information. Also, the database says that railroads did not observe the GMT+0:20 in Netherlands, yet this is a railroad journal specifically mentioning it. (Page 84) http://babel.hathitrust.org/cgi/pt?id=njp.32101066879451;view=1up;seq=98 Just leaving these here since some may be interested. Make sure the links leave you on the page # indicated -- sometimes Hathi jumps to an incorrect page. -Andrew

2 1