From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: ** X-Spam-Status: No, score=2.6 required=5.0 tests=BAYES_40,INVALID_DATE, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!caip!topaz!nike!ucbcad!ucbvax!eglin-vax!mooremj From: mooremj@eglin-vax Newsgroups: net.lang.ada Subject: A simple solution for designating time zones Message-ID: <8607021917.AA23163@ucbvax.Berkeley.EDU> Date: Wed, 2-Jul-86 15:18:02 EDT Article-I.D.: ucbvax.8607021917.AA23163 Posted: Wed Jul 2 15:18:02 1986 Date-Received: Thu, 3-Jul-86 07:10:05 EDT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Organization: The ARPA Internet List-Id: > From: Stefan.Landherr@sei.cmu.edu > ... > In addition, a calendar package with time zones should : > (1) be useful all over the world (no parochialism), > (2) cater for those places on half-hour time zones (eg South Australia), > ... > To actually designate the time zones, I recommend the usual system of letters: > Z for GMT > A, B, C, D, E, F, G, H, I, K, L, M for hours ahead of GMT > N, O, P, Q, R, S, T, U, V, W, X, Y for hours behind GMT > two-letter combinations (eg IK) for half-hour zones This is a step in the right direction, but does not go far enough. To be useful all over the world, even half-hour time zones are not sufficient; some places differ from the common time zones by 15 or 35 minutes or other odd amounts (not to mention places in the Middle East which use local sun time, which varies from day to day!) The last draft I saw of the Fortran 8x standard contained a simple solution: time zone information is stored as an integer number of minutes which must be subtracted from local time to yield GMT. Martin Moore (mooremj@eglin-vax.arpa) ------