Re: Re: Turkish/Azeri locale support
| From: | Hannes Magnusson | Date: | Wed, 05 May 2010 08:25:27 +0000 |
| Subject: | Re: Re: Turkish/Azeri locale support | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-48212@lists.php.net to get a copy of this message | ||
On Tue, May 4, 2010 at 14:14, Adam Harvey <aharvey@php.net> wrote:
> On 19 April 2010 11:58, Adam Harvey <aharvey@php.net> 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.)
+1
> 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.
There is no way this can happen. It will break massive amount of code
and will cause major headaches for people using __call().
-Hannes