Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48190 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2174 invoked from network); 4 May 2010 12:44:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 May 2010 12:44:25 -0000 Authentication-Results: pb1.pair.com smtp.mail=svanpoeck@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=svanpoeck@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: svanpoeck@gmail.com X-Host-Fingerprint: 74.125.82.170 mail-wy0-f170.google.com Received: from [74.125.82.170] ([74.125.82.170:47816] helo=mail-wy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 03/E4-04166-8A610EB4 for ; Tue, 04 May 2010 08:44:25 -0400 Received: by wyf19 with SMTP id 19so2232689wyf.29 for ; Tue, 04 May 2010 05:44:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type; bh=Lj2/K2ufEKFKLsvQAVpwG131kmi/0mX9Rjp8GM3f0VQ=; b=JnB2ha8y5h2Trxkc1XmAiXXBkVDgN7dlFEJrsn9TyDbQfzqRCpeLKIvwTxwg9DTlAP ix2TWMxPafa4AXCQdNtz+rnkZkP+pOq9cDg1Nyl21VhGn/WraG1+C/YJ8nesMuSNT32+ fezy4zPZoqjkwPliq1WIC1FZMsNEdoKrFD7Gs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:organization:user-agent:mime-version :to:cc:subject:references:in-reply-to:content-type; b=mI9vrI9KsA6U/2KKwTRxiuKyO6cttf1Vr53Gda8myM8qM00kgv7Vst4SdWJtXW28Xt HTeljD7vhbrvQEgxIqyZRGi0Kg3Er2DRac253fSMJ+hS3CyP+pIF2asinuq+Tzxx3l+c GuQFuMd6uLymAPpjN86il1F1JQnvuvnmXQ+4I= Received: by 10.227.147.195 with SMTP id m3mr1098540wbv.138.1272977061961; Tue, 04 May 2010 05:44:21 -0700 (PDT) Received: from [192.168.192.5] (host.90.30.23.62.rev.coltfrance.com [62.23.30.90]) by mx.google.com with ESMTPS id u8sm49524305wbc.17.2010.05.04.05.44.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 04 May 2010 05:44:21 -0700 (PDT) Message-ID: <4BE016A0.5020208@gmail.com> Date: Tue, 04 May 2010 14:44:16 +0200 Reply-To: Steven Van Poeck Organization: Meetic S.A. User-Agent: Thunderbird 2.0.0.24 (X11/20100411) MIME-Version: 1.0 To: internals@lists.php.net CC: Adam Harvey References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------040906020204090602090004" Subject: Re: [PHP-DEV] Re: Turkish/Azeri locale support From: svanpoeck@gmail.com (Steven Van Poeck) --------------040906020204090602090004 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Adam Harvey wrote: > On 19 April 2010 11:58, Adam Harvey wrote: > >> As at least some of you would already be aware, there's a >> long-standing issue with using PHP in a Turkish or Azeri locale, >> namely that case-insensitive lookups within the Zend engine (method >> names, for example) fail on lookups involving upper-case I characters, >> since lower-case I in those languages is ı instead of i (note the lack >> of a dot). >> > > Well, I'm going to assume that people have had whatever say they were > going to. It seems that we have three options, so let's put it to a > vote. > > (To be completely clear, this is purely for trunk. This certainly > isn't a candidate for backporting to 5.3.) > > The options are: > > 1. Apply Tomas's patch to make case-insensitive lookups > locale-ignorant. Pros: fixes immediate problem. Cons: breaks BC for > case-insensitive function/method name lookups for high-bit characters > in single-byte encodings. (Not that we've ever advertised or > documented that.) > > 2. Make function/method names case-sensitive, per Stan's e-mail. Pros: > fixes problem; brings PHP into line with most other languages; extra > consistency with variables; possible performance improvement. Cons: BC > break from current documented behaviour. > > 3. Do nothing. Pros: no BC breaks of any kind. Cons: continues to > annoy Turkish and Azeri developers and those developing for those > locales. > > If you'd care to reply with a vote for option 1, 2 or 3, I'll tally up > the votes in a week or so. And yes, I am volunteering to deal with > this should option 1 or 2 be picked. > > Adam > > No idea if I have the right to vote, but here goes: +1 for option 2 BR, Steven --------------040906020204090602090004--