Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48191 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7133 invoked from network); 4 May 2010 13:04:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 May 2010 13:04:24 -0000 X-Host-Fingerprint: 86.143.13.43 host86-143-13-43.range86-143.btcentralplus.com Received: from [86.143.13.43] ([86.143.13.43:18369] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/00-06774-F4B10EB4 for ; Tue, 04 May 2010 09:04:16 -0400 Message-ID: <52.00.06774.F4B10EB4@pb1.pair.com> To: internals@lists.php.net Date: Tue, 04 May 2010 14:04:07 +0100 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 86.143.13.43 Subject: Re: Turkish/Azeri locale support From: markskilbeck@gmail.com (Mark Skilbeck) On 04/05/2010 13:14, Adam Harvey wrote: > 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 Not that my input matters, but I vote for #2. Mark Skilbeck.