From owner-freebsd-current Fri Nov 22 19:05:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA05576 for current-outgoing; Fri, 22 Nov 1996 19:05:47 -0800 (PST) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA05571 for ; Fri, 22 Nov 1996 19:05:38 -0800 (PST) Received: (from adam@localhost) by veda.is (8.8.3/8.7.3) id DAA01233; Sat, 23 Nov 1996 03:07:39 GMT Date: Sat, 23 Nov 1996 03:07:39 GMT From: Adam David Message-Id: <199611230307.DAA01233@veda.is> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freebsd.org Subject: Re: Can anyone explain...? Newsgroups: list.freebsd.current References: <9611201540.AA19352@halloran-eldar.lcs.mit.edu> <199611201559.QAA16618@uriah.heep.sax.de> X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> As I mentioned in the commit message for the data files, MET is >> history because it never made any sense (it was sort of a bizarre >> half-translation of the German `MEZ'); all English-language references >> that the timezone maintainers were able to locate used the phrase >> ``Central European Time'', so the abbreviation was changed to match. >At least, this breaks the tradition (not only of FreeBSD). Except >IBM's AIX (which uses NFT == Norway-France-Time :), every other Unix >around calls it MET now. I think the official translation for this >was ``Mediterranean Time''. This might look a little senseless, too, >but it's IMHO a bad move to break with a traditional name once people >are used to it. >I vote for keeping the previous name. It would be worth keeping MET for backward compatibility? CET does make better sense though as the standard name. -- Adam David