From owner-freebsd-current Sun Dec 1 07:53:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA18765 for current-outgoing; Sun, 1 Dec 1996 07:53:01 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA18758 for ; Sun, 1 Dec 1996 07:52:57 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA17667 for ; Sun, 1 Dec 1996 16:52:48 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA20176 for freebsd-current@FreeBSD.org; Sun, 1 Dec 1996 16:52:48 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id QAA14162 for freebsd-current@FreeBSD.org; Sun, 1 Dec 1996 16:49:24 +0100 (MET) From: J Wunsch Message-Id: <199612011549.QAA14162@uriah.heep.sax.de> Subject: Re: Call for national time locales To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 1 Dec 1996 16:49:23 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612010857.JAA12381@freebie.lemis.de> from Greg Lehey at "Dec 1, 96 09:57:34 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Greg Lehey wrote: > >> On that subject, let me come back to harp on time zone names. If the > >> days of the week are in German, why is the time zone this deprecated > >> MET thing? Should be MEZ. > > > > Yes, but this requires much more complexity than we've got now. For > > each timezone name, you need a matrix of foreign language > > translations. > My intention was to derive it from the locale. You still didn't get it though: the timezone and the current locale are two entirely different things. There are locales like ru_RU or en_US that span quite a bunch of timezones, and there is OTOH the potential desire of somebody using a de_DE locale e.g. when he's on vacation or whatever else in California. Also, while most people prefer to get their local time, in particular many programmers aren't that happy about localization (i.e., translation) at all, and are used to work in the en_US locale all the time. As i said, it's quite more complex. The current format of the tz database isn't ready for supporting zone name localization (though i think the tz maintainers become used to that idea). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)