Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48208 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68398 invoked from network); 5 May 2010 06:44:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 May 2010 06:44:25 -0000 Authentication-Results: pb1.pair.com smtp.mail=patrick.allaert@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=patrick.allaert@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: patrick.allaert@gmail.com X-Host-Fingerprint: 209.85.160.170 mail-gy0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:39137] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 94/67-08048-8C311EB4 for ; Wed, 05 May 2010 02:44:24 -0400 Received: by gyf2 with SMTP id 2so2000107gyf.29 for ; Tue, 04 May 2010 23:44:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=1V/W+gBmoSyNyKyk2Gy1lLTj4WpMEt82AzwF5vXK9VA=; b=exzCeYBQ32g1oe8Cx5tmyOwhB/tiOuaB9CK55r3KuGIdhrar0N95MMrrHmJOQkWZK3 KvA1xDIEuK2LwEtr6nkwAG7GeRQ0Dq0KUIAAnyOKjETLrrw5tJkf2MszK9LLH7/PNTkf NlbpV1ahc1a+43z6O6sq6piGQU+ofSMGj8gFk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=umehCDgHKZb1+Cyy1MAL/IOhzn1NYJW/doSAgOTTkCm+KwNjEgRDWJb44fY+vO3UYU vIruMd8Zr3SJkb9wnTrmHoOIxNWq7fRkcF5gSrgjAt8Kt700HGO1j8n7blbKn2rMOG3a GCl2qoIJznuW9IIyzwpkIz5EhLXUD5uDnfDSA= MIME-Version: 1.0 Received: by 10.150.61.4 with SMTP id j4mr13862121yba.303.1273041861748; Tue, 04 May 2010 23:44:21 -0700 (PDT) Sender: patrick.allaert@gmail.com Received: by 10.151.47.2 with HTTP; Tue, 4 May 2010 23:44:21 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 May 2010 08:44:21 +0200 X-Google-Sender-Auth: 47d56a6bedc4f451 Message-ID: To: Adam Harvey Cc: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: Turkish/Azeri locale support From: patrickallaert@php.net (Patrick ALLAERT) 2010/5/4 Adam Harvey : > 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 =C4=B1 instead of i (note the l= ack >> 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. Once and for all: +1 for #2 (BTW that kind of BC will not be that hard to f= ix!) RMs: should this really be part of PHP 5.4 if it gets approved? > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php Patrick