From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27743 invoked by alias); 7 Dec 2002 18:46:53 -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 27730 invoked from network); 7 Dec 2002 18:46:50 -0000 Received: from unknown (HELO nescio.wildebeest.org) (62.108.28.95) by sources.redhat.com with SMTP; 7 Dec 2002 18:46:50 -0000 Received: from elsschot.wildebeest.org ([192.168.1.26] helo=localhost.localdomain) by nescio.wildebeest.org with esmtp (Exim 3.35 #1 (Debian)) id 18KjyE-0005gt-00 for ; Sat, 07 Dec 2002 19:46:34 +0100 Subject: ResourceBundle variants and child variants From: Mark Wielaard To: mauve-discuss@sources.redhat.com Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Sat, 07 Dec 2002 10:46:00 -0000 Message-Id: <1039286784.5707.18.camel@elsschot> Mime-Version: 1.0 X-SW-Source: 2002-q4/txt/msg00050.txt.bz2 Hi, Mauve contains a couple of java.util.ResourceBundle checks that test for "child variants". The Java Class Libraries, Volume 1, Second Edition explains these things and gives some examples. e.g ErrorResources_de_CH_WIN_95 and ErrorResources_de_CH_WIN_311 are both child variants of ErrorResources_de_CH_WIN. Mauve even contains some tests to check that these child variants are correctly searched for. The API Spec as found online however does not talk about child variants at all. And a quick test against the Sun JDK 1.4.1 implementation seems to suggest that it does not implement support for these child variants. Which specification should we take as normative? Do the different class libraries implementations implement it? (GNU Classpath and libgcj don't support them, kaffe does.) Should these tests be removed from Mauve? Cheers, Mark