Hello all,
we are using the TZ database on an embedded device. As the system has no
standard operating system (only a small proprietary MicroKernel) and is
not very powerful, we cannot use the TZ data "as is" on the device.
Instead of this, we create text files from the TZ data for the countries
and the time range we need on our system. The application that is used
to create these files, is written in C++ .NET (because our whole
development and deployment processes are done on Windows-based
machines).
Currently I'm using a Linux machine to compile/make the code from
tzcode*.tar.gz and to create the binary tzfiles. These binary files are
then parsed by the application mentioned above.
Is there any possibility to compile the tzcode under Windows (especially
Visual Studio 2005/2008) so that we could create our text files
automatically using only the tzcode*.tar.gz and tzdata*.tar.gz archives?
I'd appreciate any help or hints.
Best regards,
Oliver
Oliver Gerber
Diplom-Informatiker
Software Engineer
Cardinal Health Research Services
ph: +49 931 4972 276 | fax: +49 931 4972 62276
oliver.gerber(a)cardinalhealth.com
<mailto:moliver.gerber@cardinalhealth.com>
www.cardinalhealth.com/researchservices
Cardinal Health Germany 234 GmbH
Leibnizstr. 7
97204 Hoechberg, Germany
District Court Wuerzburg HRB 7004
General Management: Ralf Lother, Paul ter Grote,
Ellen de Jager-Satter, Rudy Mareel, Linda Harty
DISCLAIMER:
This information and any attachments contained in this email message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, forwarding, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email, and delete the original message immediately.
I'm forwarding this message from Andreas Radke; while Andreas is on the
time zone mailing list, the message bounced when he tried to send it
directly.
--ado
Datum: Wed, 19 Nov 2008 21:47:05 +0100
Von: Andreas Radke <a.radke(a)arcor.de>
An: tz(a)lecserver.nci.nih.gov
Betreff: optimization -O2 broken?
I'm the ArchLinux package maintainer for tzdata. We are using gcc
4.3.2/glibc2.8- We have run into a small problem with compiler
optimizations.
Using our default CFLAGS="-march=i686 -mtune=generic -O2 -pipe" the
zdump binary is built in broken way on i686 architecture. I have to
apply -O1 to make zdump work. See our bugreport:
http://bugs.archlinux.org/task/11947
I could confirm this when running zdump -v EUROPE/BERLIN it stuck after
two printing first two lines.
x86_64 architecture doesn't seem to be affected. Any idea why this
happens and how to fix it?
-Andy
Dear time zone data maintainers,
I'm a developer at ProZ.com, a website for human language translators.
One of our users has reported that the time zone names for the time
zones in Indonesia, specifically Asia/Jakarta, Asia/Pontianak,
Asia/Makassar, and Asia/Jayapura, are incorrect in the current time zone
data.
According to her, and to the following references, it appears that these
time zone abbreviations should be updated as follows:
ID offset current new
Asia/Jakarta UTC+7 WIT WIB (Waktu Indonesia Barat)
Asia/Pontianak UTC+7 WIT WIB (Waktu Indonesia Barat)
Asia/Makassar UTC+8 CIT WITA (Waktu Indonesia Tengah)
Asia/Jayapura UTC+9 EIT WIT (Waktu Indonesia Timur)
References:
http://time.kim.lipi.go.id/http://www.statoids.com/tid.html
I noticed a similar bug report from 2005 but I was unable to find any
resolution:
http://article.gmane.org/gmane.linux.debian.devel.glibc/12741/match=indones…
I hope this gives enough information to update these time zone names.
Thanks to all of you who help to maintain this valuable resource.
Best regards,
Jason Grimes
Hello, all:
Are there any Linux (SLED10, RHEL5 and Ubuntu) patches that I can download
for the latest Argentina 2008 DST rules?.
If so, could you please point me to the correct links?
Thanks in advance,
Florence
Recently I was checking the timezone map from Eric Muller (Adobe) and came
to the conclusion that he had the Kostanai (or Kustanai) area as part of the
Qyzylorda time zone although they are not even adjacent, but still on
comparatively the same longitude. The area of Kostanai I assumed was part of
the main area of Kazakhstan represented by Asia/Almaty. I am not sure where
Eric got his information from, but the story doesn't end here.
I found a russian astronomical page HYPERLINK
"http://zaytsev.com/forum/viewtopic.php?p=10571"http://zaytsev.com/forum/vie
wtopic.php?p=10571 that raises the issue that this so-called ZET 8 time is
wrong. Here is a translation from Google of the original russian article
=== Quote begin ===
Thu Apr 17, 2008 4:14 pm Posted: Thu Apr 17, 2008 4:14 pm
ZET Post: Temporary amendments to the ZET
----------------------------------------------------------------------------
----
Help solve the dilemma with the definition of a temporary correction. I was
born in Kostanai area in November 1976.
Some astrological programs, including ZET 8, provide a temporary amendment
+4 GMT. At the same time, Moscow is +3 GMT.
This means that the difference with Moscow entire 1 hour. But it never was.
The difference has always been 2 hours. And parents attest to the fact that
the difference with Moscow has always been 2 hours.
The program ZET 8 geo gives a sharp change of a temporary amendment to a
very long period:
01 Jan 0001 00:00 LMT +00:00:00 01 Jan 0001 00:00 LMT +00:00:00
02 May 1924 00:00 +04:00:00 02 May 1924 00:00 +04:00:00
21 Jun 1930 00:00 +05:00:00 21 Jun 1930 00:00 +05:00:00
01 Dec 1956 00:00 +04:00:00 01 Dec 1956 00:00 +04:00:00
01 Apr 1981 00:00 +05:00:00 01 Apr 1981 00:00 +05:00:00
In fact this change temporary amendment in 1956 is due to the change of time
zones. I can not find any information about the change of time zones in
1956, although the time change occurred not only in the Kostanai region.
This tool, please, if anyone has information about this change of temporary
amendments of 1956, which legislation has been done? Even familiar to
consultants not able to answer that question. Do not mistake that caused
even if Spravochnikov coordinates of the first edition of Cities and
temporary amendments and continually reissued by different authors ... Let
us find the truth in this matter, as he stubbornly insist that the time of
my birth at +1 GMT differs from the time in the program and is +5 GMT. I
think if I would have the rights to many "go" horoscopes ... But it is still
"a friend of Plato me, but the truth is more expensive ..."
=== Quote end ===
I guess you can't expect miracles from an automated translation. What I
understand from the email is that this person claims to have been born in
Kostanai in 1976 and that time there since has "always" been GMT+5 or rather
Moscow time plus 2 hours. This does not correspond to the Asia/Almaty time
zone but corresponds pretty well with the Asia/Qyzylorda time zone. The
thread is not faultless for instance another person grabs a part of the
World Time Explorer file Historic.txt and concludes that Astana was on GMT+5
from 1930 to 1991 while in fact the correct number is GMT+6
I might be exaggerated in assuming this is authoritative information (yet)
but all the same perhaps readers of this mailing list have more information
they can share.
The mixture of Eric's map with the administrative regions however shows
another difference that I can't explain, see the following map:
HYPERLINK
"http://www.worldtimeexplorer.com/Kustanai-2008-11-09.png"http://www.worldtimeexplorer.com/Kustanai-2008-11-09.png
The red borders are the time zones of his map. The black zones are the
recent administrative regions, as we can also see on this wikipedia map of
the Kostanai region:
HYPERLINK
"http://en.wikipedia.org/wiki/Image:Kost_obl.svg"http://en.wikipedia.org/wik
i/Image:Kost_obl.svg but Eric's map contains a bite of the Astana area.
In conclusion if the Kustanai/Kostanai region has always been on Qyzylorda
time, we don't have to do anything to Kazakhstan timezones but it would be
good to document this on the notes to the Asia/Qyzylorda time zone. Whether
the Kustanai region covers modern-time administrative area or not will then
be very important to the maps of Eric and WTE, but not directly to the tz
database. Also I think it would be good to add all current administrative
regions of Kazakhstan to the notes of the asia file.
Any comments are welcome.
- Jesper Nørgaard Welen
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 270.9.4 - Release Date: 2008-11-14 0:00
Not that anybody asked... but I thought I would provide an update on America/Resolute.
Some of you may remember that in 2006, the small community of Resolute a.k.a. "Resolute Bay" in Canada's arctic stopped the biannual practice of changing the clocks.
In March of 2007 I initiated the creation of a new Canadian zone named "America/Resolute" with a fixed time of "UTC-5".
The only web reference that I ever came across (other than my own postings) was this:
http://www.nnsl.com/frames/newspapers/2006-11/nov13_06none.html
Since there has been no recent documentation, legislation, news reports, or any other information on this subject, I decided to place a another call to the Resolute "hamlet office" last week to get an update.
I was able to confirm that Resolute is still stuck on UTC-5.
Thus the current information in the TZ database remains correct.
I will mention, however, that the residents of Resolute believe that they are changing "time zones" twice a year.
In winter months, local time is qualified with "Eastern Time" which is really "Eastern Standard Time (UTC-5)".
In summer months, local time is qualified with "Central Time" which is really "Central Daylight Time (UTC-5)".
I don't think anybody expects the TZ database to accommodate for this... as long as the offset from UTC is correct.
I did notice today that the entry for Resolute in the zone.tab says "Eastern Time - Resolute, Nunavut".
To be consistent with other Canadian zones that don't observe daylight saving time, it should probably say "Eastern Standard Time - Resolute, Nunavut".
-chris
-----Original Message-----
From: Chris Walton
Sent: March 14, 2007 11:03 AM
To: 'tz(a)elsie.nci.nih.gov'
Subject: RE: proposed tz patches for Cuba, Mongolia, Turkey, Resolute, Indonesia
A couple of weeks ago I reported that "Resolute" on Cornwallis Island in Nunavut Canada did not change its clocks on October 29/2006.
I only had one source of information.
http://www.nnsl.com/frames/newspapers/2006-11/nov13_06none.html
Today I phoned the "hamlet office" to find out what Resolute was doing with its clocks.
The individual that answered the phone confirmed that the clocks did not move at the end of daylight saving on October 29/2006.
He also told me that the clocks did not move this past weekend (March 11/2007).
He was not sure whether to refer to the local time as "Eastern Time" or "Central Time" but we did a quick time check comparing his clock vs my clock and I was able to confirm that Resolute is currently running on UTC-5.
The implication is that Resolute has been on UTC-5 (Eastern Standard Time or Central Daylight Time) since April 2/2006.
I was also told that the hamlet council has not officially announced what will happen next fall.
Apparently there was confusion for residents when the time did not change last October... specifically with respect to television schedules.
America/Resolute should use the "Canada" Rule up to October 29/2006.
After that it should be fixed on Eastern Standard Time until further notice.
-chris
I have developed a time zone systems that uses ISO-3166
AnyDateTime CREATED BOLD DARING NEW TECHNIQUES.
The results had amazing results:
· Incredible speed.
· Incredible capabilities.
· Incredible simplicity.
The results are exciting, but striving for perfection required tremendous
tenacity but was very satisfying.
AnyDateTime¾USES INTERNATIONAL STANDARDS.
Date/time format conversion.
Uses the ISO-8601 (International Organization for Standardization) date/time
formats.
The Internet XML requires the use of this format.
· Converts North America formats 06/18/2008 01pm to the common
world use of 18.06.2008 13:00 or the international standard 2008-06-18T13:00:00
· Features that are unique to international ISO-8601 standard are
implemented into local date/time formats. Therefore, an international
date/time can be converted to a local date/time and back to the international
date/time.
Date/time time-zone conversion.
Uses the ISO-3166 location codes for countries and states.
· The same codes used to mail letters are used to converting US EST
(EDT) to CST (CDT), MST (MDT), PST (PDT), AST (ADT) or HST or anywhere else
in the world.
Uses the IATA city codes (International Air Transport Association).
· The same 3 letter code on your airline luggage can be used for
time zone conversion and currency conversion.
Date/time manipulation.
Uses the ISO-8601 durations.
· The ISO-8601 duration “PnYnMnDTnHnMnS” is used for working with
years, months, days, hours, minutes, seconds or fractions of time regardless
of MM/DD/YYYY, DD.MM.YYYY or YYYY-MM-DD format.
Adding/subtracting date/time
Setting date/time to a specific date/time, like the start and ending of
daylight.
Getting date/time for different formats like “6/18/2008 1pm” or “2008-01-18
13:00”
Comparing different formats equal
“06/18/2008 6pm-05;00” = “2008-06-19 01:00+02:00”
Finding the difference in years, hours, days, hours, minutes, seconds or in
combinations of elements.
· Created a new “Event Algebra” by expanding the ISO-8601
durations “=±P=±nY=±nM=±nD=±T=±nH=±nM=±nS=±.nF”.
The event of the start of daylight saving time is:
The 3rd month, the 2cd week, on the 1st day of the week at 2am
The formula =03m14d-1dwT=2h
This is much simpler than the Microsoft’s Excel or Visual Basic methods.
Currency conversion.
Global selling requires currency conversion as well as time conversions.
The same way is sued for currency conversion as is used for time zone
conversion.
AnyDateTime UNIQUE CREATIONS.
Created the fastest time zone conversion routine in the world.
For the first time every, computers can do simultaneous mixed-radix
arithmetic. If it is plugged into the C/C++ conversions routines or IBM’s durations
routines they run 2.75 time faster.
Created the fastest date/time validation routines in the world.
The checking for 30 and 31 day months and leap years is so fast it is almost
un-measurable for a million date/time checks, so it is always on.
Java date/time check is so slow it permits it to be turned off for speed.
IBM’s date/time almost doubles the CPU usage if date/time is checked.
C/C++ requires programmers to write their own 30 day month check else it
converts
2008-06-31 to 2008-07-01 without error indicator.
Created “Event Algebra” that simplifies event calculation and provides a
standard method for event calculation.
The ISO-8601 duration “PnYnMnDTnHnMnS” has been expanded to create “Event
Algebra”.
Created an Internet auto synchronization for client table update.
When North America changed the daylight savings time, your computer was
updated automatically over the Internet. However, companies doing business
over around the world need the time zones of everywhere in the world. Those
nice time zone lines on maps or computer screens are no more than approximations
and don’t reflect daylight savings time.
The advantages of a local service:
· A local service program can do in minutes what takes days using a
Web-service.
· The auto-synchronization feature give local services the same
features as Web-services, it updates the tables on the client computer without
any manual intervention.
The risks with Web-services:
· Some applications kill Internet performance, so all other
applications suffers.
· The potential for gouging by application service providers (ASP).
· No control over ASP performance or quality.
The disadvantage of other local services:
· Other date/time routines use the “tz.database” that must be
compiled on the client’s computer and requires manually intervention to put into
production.
AnyDateTime date/time data type has incredible capabilities.
Herman J Woudenberg
The world’s largest date range has a worlds largest date range of 2 million
years (±1 million –1 year).
UNIX/LINUX JAVA & C/C++ have a date range of 68 years, 1970 to 2038.
ANSI COBOL-90 has a date range from 1601 to 9999.
IBM Power PC computer has a date range from 1483 to 9999.
Microsoft .NET (Vista) has a date range from 0001 to 9999.
Microsoft Com (XP) has a date range from 1600 to 9999.
Oracle has a date range from 4500BC to 9999 AD.
The world’s smallest time precision as small as femto-seconds, 15 fractional
digits_[i]_ (aoldb://mail/write/template.htm#_edn1) .
UNIX and C only have whole seconds, no fractions of seconds.
Java has milliseconds, 3 fractional digits.
IBM has up to microseconds, 6 fractions digits.
Microsoft has 100 nanoseconds, about 7 fractional digits.
Oracle has up to 9 fractions digits.
Network Time Protocol has 10 fractional digits.
____________________________________
_[i]_ (aoldb://mail/write/template.htm#_ednref1) Fractions of seconds.
Milli-second (ms or msec) is one thousandth of a second (.999 or 10-3).
It is used for read/write time of hard disk or CD-ROM and packet travel time
on the Internet.
Micro-second (us or Greek letter mu plus s) is one millionth (.999_999 or
10-6) of a second.
It is used to measure the speed of CPUs.
Nano-secnd (ns or nsec) is one billionth (.999_999_999 or 10-9) of a second.
It is used for read/write time of random access memory (RAM).
Pico-second is one trillionth (.999_999_999_999 or 10-12) of a second, or
one millionth of a microsecond.
It is used by the Net Work Time Protocol clock.
Femto-second is one millionth of a nanosecond (.999_999_999_999_999 or
10-15) of a second.
It is used in laser technology.
Atto-second is one quintillionth (.999_999_999_999_999_999 or 10-18) of a
second.
It is a used in photon research.
**************Get the Moviefone Toolbar. Showtimes, theaters, movie news &
more!(http://pr.atwola.com/promoclk/100000075x1212774565x1200812037/aol?red…p://toolbar.aol.com/moviefone/download.html?ncid=emlcntusdown00000001)
Vernon Cole claimed to me that we need a new time zone for West Wendover,
Nevada. After checking the case I think he is right.
West Wendover lies close to Wendover, Utah, but according to state border
application they are on Pacific time while Wendover is on Mountain time.
West Wendover seems to have a history long back of using Mountain time for
convenience, but that use was never official. The main reason is that every
most relations to other geographic locations close-by will be using Mountain
time, and the bigger cities on the Nevada region are 100 miles or more from
West Wendover. Apparently real problems began in the eighties and nineties
when the city council began to insist on using Pacific time officially. In
1999 the DOT approved an application from West Wendover about shifting to
Mountain time officially and on a permanent basis, using DST etc. The exact
moment of application was opportune, the 31.st. of October 1999 at 2:00 PDT
(GMT-7) when most of Nevada went back to PST (GMT-8) then West Wendover just
stayed on GMT-7 (Mountain Standard Time).
The case of the Nevada northern border (Jackpot, Owyhee, and Mountain City),
which is also using Mountain time is different, because they seem to have
been using Mountain time "always" so they can use time zone America/Denver.
The legislation is resumed here:
HYPERLINK
"http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=1999_register&doc
id=99-27240-filed"http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=
1999_register&docid=99-27240-filed
There is some of the history on the Wikipedia page:
HYPERLINK
"http://en.wikipedia.org/wiki/West_Wendover"http://en.wikipedia.org/wiki/Wes
t_Wendover
Jesper Nørgaard Welen
Email: jnorgard(a)Prodigy.Net.mx
Project Leader (Líder de Proyecto) Software
CIMMYT - Centro Internacional de Mejoramiento de Maíz y Trigo
Dirección: CIMMYT Int. c/o Jesper Nørgaard
Km. 45, Carretera México-Veracruz
El Batán
Texcoco, Edo. de México
CP 56130 MEXICO
Tel.: +52 (55) 58-04-20-04 ext. 1374
Fax: +52 (55) 58-04-75-58
Tel. Casa: 53-10-05-95 ó 53-10-97-78
Download the shareware program World Time Explorer, I made:
HYPERLINK
"http://www.worldtimeexplorer.com/index.html"http://www.worldtimeexplorer.co
m/index.html
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 270.9.0/1772 - Release Date: 2008-11-06
20:23
