From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2069 invoked by alias); 10 Dec 2002 20:23:20 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 2061 invoked from network); 10 Dec 2002 20:23:18 -0000 Received: from unknown (HELO nescio.wildebeest.org) (62.108.28.95) by sources.redhat.com with SMTP; 10 Dec 2002 20:23:18 -0000 Received: from elsschot.wildebeest.org ([192.168.1.26] ident=mark) by nescio.wildebeest.org with esmtp (Exim 3.35 #1 (Debian)) id 18Lqu3-0004zv-00; Tue, 10 Dec 2002 21:22:51 +0100 Subject: Re: ResourceBundle variants and child variants From: Mark Wielaard To: Dalibor Topic Cc: Andrew Haley , mauve-discuss@sources.redhat.com In-Reply-To: <20021210164514.8588.qmail@web10006.mail.yahoo.com> References: <20021210164514.8588.qmail@web10006.mail.yahoo.com> Content-Type: text/plain Organization: Message-Id: <1039551787.7415.50.camel@elsschot> Mime-Version: 1.0 Date: Tue, 10 Dec 2002 12:23:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2002-q4/txt/msg00058.txt.bz2 Hi, On Tue, 2002-12-10 at 17:45, Dalibor Topic wrote: > I think I remember the time when there were child > variants for *Locales* in wide useage in the EU, due > to pending conversion to a new currency. de_DE_EURO > anyone? Actually that is a "normal variant". A Locale with a child variant would be de_DE_EURO_POSIX or de_DE_POSIX_EURO. (Hmmm, makes you think, what is more important, EURO or POSIX?) > As I understand the spec for Locale, it says "Where > there are two variants, separate them with an > underscore, and put the most important one first." , > so it is possible to have child variants. They also > give an example in the next sentence, > "Traditional_WIN" . See > http://java.sun.com/j2se/1.4/docs/api/java/util/Locale.html > , the paragraph just below the country code link. So they do exist :) I think what happened is that ResourceBundle got rewritten so many times (the Sun bug database has a lot of bug reports about it being rewritten once again) that the original algorithm that just chopped off a '_' at a time somewhere got lost. And that the new specification now just explains what this new algorithm does (take the Locale variant as one string). Sigh, I really wish there was a real Java standard. But I didn't find any bug reports about people missing the child variant support in the first place so maybe it just wasn't a very useful feature in the first place. I don't think that it is such a slam-dunk as Andrew says but removing (or disabling) these tests does make sense. Does anybody disagree? Cheers, Mark