-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
font-family: helvetica, arial, sans-serif;
<h3>How do I use jsTimezoneDetect?</h3>
- This script gives you the zone info key representing your device's time zone setting.
+ This script gives you the zone info key representing your device's time zone setting.
It is synchronous, fast and about 1.65 KB gzipped (4.9 KB uncompresse d).
- <a href="https://bitbucket.org/pellepim/jstimezonedetect/downloads#download-38156">Download
- the latest minified version here</a>. Include it on a webpage. Then:
+ The IANA timezone database is pretty much standard for most platforms (UNIX and Mac support it natively, and every programming language in the world either has native support or well maintained libraries that support it).
+ There is a minified version in the repo called `jstz.min.js`. Include it in your HTML document.
+ Invoke the script by calling
<pre id="code-example" class="prettyprint">
>>> var timezone = jstz.determine_timezone();
-<h3>What do I do with the result?</h3>
-<p class="instructions">Use the time zone key to do datetime normalizations across time zones.</p>
-<p class="instructions">The key is compliant with the zoneinfo database, often called the "Olson database".
-<p class="instructions">Every programming language in the world worth the name supports the zoneinfo database, or has libraries that does.</p>
+ The script is useful if you do not want to disturb your users with questions about what time zone they are in. You can rely on this script to give you a key that is usable for server side datetime normalisations across time zones. </p>
+<p class="instructions">This script does not do geo-location, nor does it care very much about historical time zones. </p>
-<h3>How do I test this script?</h3>
-<p class="instructions">To test the detection script, simply change your system timezone, <strong>restart
- the browser</strong>, and open this page again.
- Firefox and Internet Explorer do not seem to require restarting the browser.
+<p class="instructions">So if you are unhappy with the time zone "Europe/Berlin" when the user is in fact in "Europe/Stockholm" - this script is not for you. (They are both identical in modern time).</p>
-<h3 class="omg">I don't like the timezone this script gives me!</h3>
-<p class="instructions">If you are looking for historically and/or geographically precise
- timezones. <strong>jsTimezoneDetect is not for you</strong>.</p>
-<p class="instructions">This script does not do geolocation. It simply picks the most populated
- timezone among several identical ones (in modern time).</p>
-<p class="instructions">For example, it is hard to quickly distinguish between different timezones
- in central Europe. And often it is not needed, since they are all the same in modern time.</p>
- This script will return Europe/Berlin regardless of where you live in the
- Central European timezone. Even though <strong>Europe/Amsterdam</strong> and
- <strong>Europe/Berlin</strong> are historically different, nowadays they are idential.</p>
- <a href="https://bitbucket.org/pellepim/jstimezonedetect/wiki/Detection_List">Click here for
- the list of timezones this script is able to detect</a>.</p>
+<p class="instructions">Also, if it is important to you to know that in Europe/Simferopool (Ukraine) the UTC offset before 1924 was +2.67, sorry, this script will not help you.</p>
+<p class="instructions">Time zones are a screwed up thing, generally speaking, and the scope of this script is to solve problems concerning modern time zones, in this case from 2010 and forward.</p>
<p class="instructions">If this script fails to correctly determine your timezone, <a href="https://bitbucket.org/pellepim/jstimezonedetect/issues/new">please report it!</a></p>
<p class="instructions">When you report an issue. Please tell me </p>