From dev-return-23937-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Tue Apr 12 16:56:49 2011 Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 73188 invoked from network); 12 Apr 2011 16:56:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Apr 2011 16:56:48 -0000 Received: (qmail 94752 invoked by uid 500); 12 Apr 2011 16:56:48 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 94683 invoked by uid 500); 12 Apr 2011 16:56:48 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 94675 invoked by uid 99); 12 Apr 2011 16:56:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Apr 2011 16:56:48 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of trawick@gmail.com designates 209.85.214.50 as permitted sender) Received: from [209.85.214.50] (HELO mail-bw0-f50.google.com) (209.85.214.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Apr 2011 16:56:41 +0000 Received: by bwz2 with SMTP id 2so8416072bwz.37 for ; Tue, 12 Apr 2011 09:56:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=2YqRWKjSGLA6om6igusQ2RqwhKLLeBcxc2wAUSYT4lM=; b=g5K1vI3/dHZvA6755HO86e7DL1NKxzd5SuTVcg/fUDzWAB3z22L+XG7PD7TN5Ph4Oy xPh3as03HyK79LywTOt+3tFR+Mk3eT3CdNyq/0bFMAKwXey12BHHUiwiV3xXP7gR5Irw X9jM6Z24De6NHA+6nQtmFDmfZmwMAQ4SMLwcA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=cRRviu26MEIPdyuTrmNc72f/Jsi1ZiAvPN1mconbQtRuEwRAytHPhhpTTcja0vmY7R zHZrPwmRd/L43eGO8r93ZL2xc86IdwkxFawxColCKzBZ+A7FGr8t/Y1eWB716vaodJHp /y3tVXzXM/2UqityZgfjjPH0IP2I7yktRNdjI= MIME-Version: 1.0 Received: by 10.204.32.9 with SMTP id a9mr1024000bkd.182.1302627380948; Tue, 12 Apr 2011 09:56:20 -0700 (PDT) Received: by 10.204.16.207 with HTTP; Tue, 12 Apr 2011 09:56:20 -0700 (PDT) In-Reply-To: <4DA47DF9.1040002@rowe-clan.net> References: <4DA47DF9.1040002@rowe-clan.net> Date: Tue, 12 Apr 2011 12:56:20 -0400 Message-ID: Subject: Re: i18n codepage guidance needed From: Jeff Trawick To: APR Developer List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Apr 12, 2011 at 12:29 PM, William A. Rowe Jr. wrote: > I have one dev question for my apr_fnmatch() refactoring > > Today we lowercase the two characters (and don't support case-insensitive > range matches at all, I won't change this apr-specific quirk). =A0But IIR= C > there are language with multiple lower case representations of the same > upper case character, but never (or at least, rarely) visa versa? > > Shouldn't we upcase both the text and match chars, instead, to better > support non-ASCII locales? =A0(Obviously, this ignores utf-8 issues, and > I'm not going to enable MBCS in this next release, but will at least make > it possible to enhance for MBCS later on, without changing fn prototypes)= . No real answer, just some comments... * FWLIW, it is tolower() now "just because." It was originally toupper(). * For interesting text, it could change behavior, and we don't have bugs filed now, right? * For interesting text, neither toupper() nor tolower() nor =3D=3D is correct! (So don't bother changing behavior.)