From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6118 invoked by alias); 16 Feb 2003 11:54:12 -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 6110 invoked from network); 16 Feb 2003 11:54:10 -0000 Received: from unknown (HELO nescio.wildebeest.org) (62.108.28.95) by 172.16.49.205 with SMTP; 16 Feb 2003 11:54:10 -0000 Received: from elsschot.wildebeest.org ([192.168.1.26] ident=mark) by nescio.wildebeest.org with esmtp (Exim 3.35 #1 (Debian)) id 18kNMY-0002UY-00; Sun, 16 Feb 2003 12:53:38 +0100 Subject: Re: new test cases (long) From: Mark Wielaard To: raif@fl.net.au Cc: Mauve In-Reply-To: <200302151101.21183.raif@fl.net.au> References: <200302090318.02317.raif@fl.net.au> <1045223836.30202.326.camel@elsschot> <200302151101.21183.raif@fl.net.au> Content-Type: text/plain Organization: Message-Id: <1045396437.30179.522.camel@elsschot> Mime-Version: 1.0 Date: Sun, 16 Feb 2003 11:54:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q1/txt/msg00026.txt.bz2 Hi Raif, Thanks for all the pointers. The character encoding names seem to be confusing whatever way you look at it. What is and isn't a canonical name, for what package, what the (historical) alias is, etc is difficult to decipher. Also note that the 1.4 docs and 1.4.1 encoding docs actually list different canonical names... Duh... Anyway I think the best thing todo is to add all canonical, historical and/or alias must support character names to the getBytes() tests, at least for the names that are documented on all these different (versions) of the API/Spec pages. The distinction between names used for java.lang/io and java.nio seems to only confuse matters and implementations that only support some names for some of the library classes will probably confuse users enormously. So getBytes14 now tests US-ASCII, windows-1252, ISO-8859-1, ISO-8859-15, ISO8859_15, UTF-16BE and UTF-16LE. Together with the getBytes13 tests this should catch all the encoding names that people will probaly always expect to be available in a normal class library implementation. Cheers, Mark