Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 93904 invoked from network); 12 Sep 2006 06:44:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Sep 2006 06:44:50 -0000 Received: (qmail 22651 invoked by uid 500); 12 Sep 2006 06:44:48 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 22596 invoked by uid 500); 12 Sep 2006 06:44:48 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 22583 invoked by uid 99); 12 Sep 2006 06:44:47 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Sep 2006 23:44:47 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_NEUTRAL,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: 202.81.18.155 is neither permitted nor denied by domain of roberthurui@gmail.com) Received: from [202.81.18.155] (HELO ausmtp06.au.ibm.com) (202.81.18.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Sep 2006 23:44:46 -0700 Received: from sd0208e0.au.ibm.com (d23rh904.au.ibm.com [202.81.18.202]) by ausmtp06.au.ibm.com (8.13.6/8.13.6) with ESMTP id k8C6jdjM5357590 for ; Tue, 12 Sep 2006 16:45:39 +1000 Received: from d23av01.au.ibm.com (d23av01.au.ibm.com [9.190.250.242]) by sd0208e0.au.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id k8C6llXt244148 for ; Tue, 12 Sep 2006 16:47:47 +1000 Received: from d23av01.au.ibm.com (loopback [127.0.0.1]) by d23av01.au.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k8C6iMMh002739 for ; Tue, 12 Sep 2006 16:44:22 +1000 Received: from d23m0011.cn.ibm.com (d23m0011.cn.ibm.com [9.181.32.74]) by d23av01.au.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k8C6iJ2F002642 for ; Tue, 12 Sep 2006 16:44:22 +1000 Received: from [127.0.0.1] ([9.181.107.82]) by d23m0011.cn.ibm.com (Lotus Domino Release 6.5.5HF262) with ESMTP id 2006091214430711-16096 ; Tue, 12 Sep 2006 14:43:07 +0800 Message-ID: <4506573B.5000304@gmail.com> Date: Tue, 12 Sep 2006 14:44:11 +0800 From: Robert Hu Reply-To: roberthurui@gmail.com Organization: IBM CDL User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: harmony-dev@incubator.apache.org Subject: Re: [classlib][luni]difference between RI and ICU References: <211709bc0609112321r7d644378s5ceefbb56bea234e@mail.gmail.com> In-Reply-To: <211709bc0609112321r7d644378s5ceefbb56bea234e@mail.gmail.com> X-MIMETrack: Itemize by SMTP Server on D23M0011/23/M/IBM(Release 6.5.5HF262 | April 5, 2006) at 12/09/2006 14:43:07, Serialize by Router on D23M0011/23/M/IBM(Release 6.5.5HF262 | April 5, 2006) at 12/09/2006 14:43:12 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Tony Wu =E5=86=99=E9=81=93: > I encounter a problem when implement isWhiteSpace(int) in j.l.Character. > There is a difference between RI and ICU. > > RI spec says, > > >> It is a Unicode szpace character (SPACE=5FSEPARATOR, LINE=5FSEPARATOR, or >> PARAGRAPH=5FSEPARATOR) but is not also a non-breaking space ('\u00A0', >> '\u2007', '\u202F'). Anyway, spec is our first rule to follow. > but ICU spec says, > >> It is a Unicode space separator (category "Zs"), but is not a no-break >> space (\u00A0 or \u202F or \uFEFF). > > RI excludes U+2007 however ICU excludes U+FEFF > > And I looked up the definition of these 4 related characters on=20 > unicode.org: > >> 00A0;NO-BREAK SPACE;Zs;0;CS; 0020;;;;N;NON-BREAKING SPACE;;;; >> 2007;FIGURE SPACE;Zs;0;WS; 0020;;;;N;;;;; >> 202F;NARROW NO-BREAK SPACE;Zs;0;CS; 0020;;;;N;;;;; >> FEFF;ZERO WIDTH NO-BREAK SPACE;Cf;0;BN;;;;;N;BYTE ORDER MARK;;;; So cool... :-) > > I consider it is a bug of ICU because the U+FEFF is not in category=20 > *Zs* as > ICU spec described. And I purposed to report that to ICU team. > Should I handle the U+2007 by ourselves to follow RI or just document=20 > this > problem in testcase? > IMO, it's natural to follow RI, and the challenge is to fix it=20 gracefully with ICU implementation. --=20 Robert Hu China Software Development Lab, IBM --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org For additional commands, e-mail: harmony-dev-help@incubator.apache.org