<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Handwriting";
panose-1:3 1 1 1 1 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I’m trying to get this mail through to the email list & it gave me an error.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Can you help me get it through? If you already received it through my attempt, please disregard.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Here’s the message:<o:p></o:p></span></p><p class=MsoNormal>Hello list,<o:p></o:p></p><p class=MsoNormal>I am also a Timezone newbie.<o:p></o:p></p><p class=MsoNormal>I need to get a dump of the tz database for all countries in the world, which timezone they are in, and what date they switch on/off DST. I’m not interested in getting real time dates; I just need a refresh of the database periodically.<o:p></o:p></p><p class=MsoNormal>Can somebody tell me how I would get this? Is there a site that I can get the data from?<o:p></o:p></p><p class=MsoNormal>Thanks<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Lucida Handwriting";color:#17365D'>Bonnie K. O'Neil<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>CBIP, CDMP<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Enterprise Data Architect<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Travelport Global Technology Solutions<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Office: 303-397-5239<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mobile: 303-725-1737<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> yoshito_umaoka@us.ibm.com [mailto:yoshito_umaoka@us.ibm.com] <br><b>Sent:</b> Friday, February 04, 2011 9:00 AM<br><b>To:</b> tz@lecserver.nci.nih.gov<br><b>Subject:</b> How about adding UN/LOCODE in zone.tab?<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Related to the post below.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Unicode CLDR defines locale identifiers based on BCP47 language tag (</span><a href="http://www.ietf.org/rfc/bcp/bcp47.txt"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>http://www.ietf.org/rfc/bcp/bcp47.txt</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>)</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>BCP47 provides a mechanism for extending language tags for use in various applications.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>We recently published RFC6067 (</span><a href="http://datatracker.ietf.org/doc/rfc6067/"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>http://datatracker.ietf.org/doc/rfc6067/</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>) to allocate BCP47 extension letter "u" for the use of Unicode Locale Identifiers. Unicode Locale Identifier has its own subtag for specifying time zone IDs. Unfortunately, zone IDs in the tz database cannot be used in language tag because each subtag in extension must be 2 to 8 alpha/numeric characters. For this reason, we defined "short ID" for zones based on UN/LOCODE [</span><a href="http://www.unece.org/cefact/locode/"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>http://www.unece.org/cefact/locode/</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>]. Most of exemplar cities by the tz database are covered by LOCODE, with small exceptions.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>For example, zone "America/New_York" is represented by "usnyc". The mapping data is provided in the file - </span><a href="http://www.unicode.org/repos/cldr/trunk/common/bcp47/timezone.xml"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>http://www.unicode.org/repos/cldr/trunk/common/bcp47/timezone.xml</span></a> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>With the extension, you can exchange locale data including time zone information with a language tag - for example, "en-US-u-tz-usnyc"</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I'm wondering if zone.tab can include LOCODE - for example, LOCODE consist from ISO3166 2-letter country code + 3-letter location code.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>#locode coordinates TZ comments</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>AD ALV +4230+00131 Europe/Andorra</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>AE DXB +2518+05518 Asia/Dubai</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>AF KBL +3431+06912 Asia/Kabul</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>AG ANU +1703-06148 America/Antigua</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>...</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>-Yoshito Umaoka (ICU / CLDR project)</span> <br><br><br><tt><span style='font-size:10.0pt'>Hjwoudenberg <hjwoudenberg@aol.com> wrote on 02/03/2011 07:23:00 PM:</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><br><tt>> From: Hjwoudenberg <hjwoudenberg@aol.com></tt></span> <br><tt><span style='font-size:10.0pt'>> To: <tz@lecserver.nci.nih.gov></span></tt> <br><tt><span style='font-size:10.0pt'>> Date: 02/03/2011 07:30 PM</span></tt> <br><tt><span style='font-size:10.0pt'>> Subject: RE: lat/lon time offset database</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> For time zones I use ISO 3166 country codes and state codes.</tt></span> <br><tt><span style='font-size:10.0pt'>> For some states I need a suffix like 'n' or 'w' or 's' or 'e' if </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> the state has more than one time zone.</tt></span> <br><tt><span style='font-size:10.0pt'>> It also can use the IATA city code, the 3 letter code on your airline luggage.</span></tt> <br><tt><span style='font-size:10.0pt'>> It contains the time zone rules so each year it calculates the new </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> dates for daylight.</tt></span> <br><tt><span style='font-size:10.0pt'>> The rules can be updated on demand, when used first time each year, </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> over the Internet. </tt></span><br><tt><span style='font-size:10.0pt'>> It also contains the ISO country name, state name and city name and </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> airport name.</tt></span> <br><tt><span style='font-size:10.0pt'>> Hope fully the lat/lon for states and countries will someday be </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> available even if they approximate coastlines. </tt></span><br><tt><span style='font-size:10.0pt'>> These should be a suggestion for the Unicode </span></tt><br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt><a href="http://cldr.unicode.org/"><tt><span style='font-size:10.0pt'>http://cldr.unicode.org/</span></tt></a> <br><tt><span style='font-size:10.0pt'>> CLDR Project</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> The Unicode CLDR provides key building blocks for software to </tt><br><tt>> support the world's languages, with the largest and most extensive </tt><br><tt>> standard repository of locale data available. This data is used by a</tt><br><tt>> wide spectrum of companies for their software internationalization </tt><br><tt>> and localization, adapting software to the conventions of different </tt><br><tt>> languages for such common software tasks as:</tt></span> <br><tt><span style='font-size:10.0pt'>> formatting of dates, times, and time zones, </span></tt><br><tt><span style='font-size:10.0pt'>> formatting numbers and currency values</span></tt> <br><tt><span style='font-size:10.0pt'>> sorting text</span></tt> <br><tt><span style='font-size:10.0pt'>> choosing languages or countries by name</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt><a href="http://cldr.unicode.org/index/processIntroduction"><tt><span style='font-size:10.0pt'>http://cldr.unicode.org/index/processIntroduction</span></tt></a> <br><tt><span style='font-size:10.0pt'>> This document describes the Unicode CLDR Technical Committee, and </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> its process for data collection, resolution, public feedback and </tt><br><tt>> release. The process is designed to be light-weight: in particular, </tt><br><tt>> the meetings are frequent, short, and informal. Most of the work is </tt><br><tt>> by email or phone, with a database recording requested changes in data.</tt></span> <br><tt><span style='font-size:10.0pt'>> When gathering data for a region and language, it is important to </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> have multiple sources for that data to produce the most widely </tt><br><tt>> acceptable data. Initial versions of data were based on the best </tt><br><tt>> available sources, but CLDR data will be modified and improved, in </tt><br><tt>> successive versions, by more input from the contributors inside and </tt><br><tt>> outside of the Unicode Consortium.</tt></span> <br><tt><span style='font-size:10.0pt'>> It is important to note that CLDR is a Repository, not a </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> Registration. That is, contributors should not expect that their </tt><br><tt>> contributions will simply be adopted into the repository; instead, </tt><br><tt>> it will be vetted against the best available information.</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> </tt></span> <br><tt><span style='font-size:10.0pt'>> Herman J Woudenberg</span></tt> <br><tt><span style='font-size:10.0pt'>> -----Original Message-----</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> From: Chris Walton <Chris.Walton@telus.com></tt><br><tt>> To: tz@elsie.nci.nih.gov <tz@lecserver.nci.nih.gov>; larry.ober </tt><br><tt>> <larry.ober@att.net></tt><br><tt>> Sent: Thu, Feb 3, 2011 5:37 pm</tt><br><tt>> Subject: RE: lat/lon to time offset database</tt><br></span><br><tt><span style='font-size:10.0pt'>> Larry,</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> Just so you know that it is possible… some of the newer GPS units on</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> the market today are capable of automatically determining the local time zone.</tt></span> <br><tt><span style='font-size:10.0pt'>> This is achieved with proprietary time zone maps that are installed </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> inside the GPS at the factory.</tt></span> <br><tt><span style='font-size:10.0pt'>> Newer versions of the maps are bundled inside firmware images so </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> that you automatically get the latest map when you upgrade the </tt><br><tt>> firmware on your GPS.</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> If these built in time zone maps are not accurate (or if you find </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> yourself in an area with disputed time zones), it is possible to </tt><br><tt>> turn off automatic mode and then manually enter the time zone of </tt><br><tt>> your choosing.</tt></span> <br><tt><span style='font-size:10.0pt'>> A Google search reveals that one of the GPS manufacturers stores its</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> time zone data in a file that is approximately 600kB.</tt></span> <br><tt><span style='font-size:10.0pt'>> I think we can assume that the data in this file is written in a </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> very heavily compressed format; it could theoretically be many </tt><br><tt>> megabytes if uncompressed.</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> -chris</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> From: Larry Ober [</span></tt><a href="mailto:larry.ober@att.net"><tt><span style='font-size:10.0pt'>mailto:larry.ober@att.net</span></tt></a><tt><span style='font-size:10.0pt'>] </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> Sent: February 3, 2011 2:27 PM</tt><br><tt>> To: tz@lecserver.nci.nih.gov</tt><br><tt>> Subject: Re: lat/lon to time offset database</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> Hi John,</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> Well there would be some level of accuracy question. The more </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> accurate the polygon the larger the database. Also if the lat/lon </tt><br><tt>> data was provided by GPS, there is the question of signal availability.</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> Basically it just seems dumb that I need to tell my GPS what time </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> zone it's in. LOL</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> Best Regards</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> Larry</span></tt> <br><tt><span style='font-size:10.0pt'>> ----- Original Message ----- </span></tt><br><tt><span style='font-size:10.0pt'>> From: John Haxby </span></tt><br><tt><span style='font-size:10.0pt'>> To: tz@lecserver.nci.nih.gov </span></tt><br><tt><span style='font-size:10.0pt'>> Sent: Thursday, February 03, 2011 1:54 PM</span></tt> <br><tt><span style='font-size:10.0pt'>> Subject: Re: lat/lon to time offset database</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> On 3 Feb 2011, at 18:33, Larry Ober wrote:</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br></span><br><tt><span style='font-size:10.0pt'>> I am looking at building a small embedded system (No OS) that will require </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> determining the local time from the lat/lon of a location. So </tt><br><tt>> basically I need </tt><br><tt>> lat/lon to time offset from "GMT".</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> Does that work? I'm sure I can find places in Spain that are that </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> are close to Lisbon than they are Madrid but being in Spain the </tt><br><tt>> timezone should be Europe/Madrid. Also, when you're on going </tt><br><tt>> through the channel tunnel do you go from being closer to Paris than</tt><br><tt>> you are to London only when you've left Calais? Or before you get to Dover?</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> Or have I got hold of the wrong end of the sti </span></tt><o:p></o:p></p></div></body></html>
<pre>If you are not the intended recipient of this e-mail message, please notify the sender
and delete all copies immediately. The sender believes this message and any attachments
were sent free of any virus, worm, Trojan horse, and other forms of malicious code.
This message and its attachments could have been infected during transmission. The
recipient opens any attachments at the recipient's own risk, and in so doing, the
recipient accepts full responsibility for such actions and agrees to take protective
and remedial action relating to any malicious code. Travelport is not liable for any
loss or damage arising from this message or its attachments.