Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32025
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain users.sourceforge.net from 213.197.162.99 cause and error)
Message-ID: <36616.78.61.224.253.1188837207.squirrel@avilys.eik.lt>
In-Reply-To: <1188820136.3317.3.camel@localhost.localdomain>
References: <60461.195.22.180.233.1188818194.squirrel@avilys.eik.lt>
    <1188820136.3317.3.camel@localhost.localdomain>
Date: Mon, 3 Sep 2007 19:33:27 +0300 (EEST)
To: jani.taskinen@iki.fi
Cc: internals@lists.php.net
User-Agent: NaSMail/1.2
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] PHP bugs in Turkish locale
From: tokul@users.sourceforge.net ("Tomas Kuliavas")

I'll add comments on 35050 and you will ignore it, because bug is not open.

You have patch on http://bugs.php.net/bug.php?id=35583. I understand why
it might have been rejected. Using mapping table to lowercase ascii is not
optimal solution.

I have other patch, but you are not free to use code licensed under GPL. I
am not C programmer and this patch uses code taken from program licensed
under GPL.

I've noticed one change. strcasecmp() is no longer locale aware. PHP does
not have regression test for 19795 bug or this test depends on locale that
is not available on my machine. strtolower(), strtoupper() and stristr()
are still locale aware. Currently I am not testing other string functions.

> You are free to send a patch.. :)
>
> If you have objections, please add comment to the report marked as "Wont
> fix" and don't spam the already huge database with one more report about
> same issue.
>
> --Jani
>> Hi,
>>
>> Maybe somebody could provide good explanation why you can fix the issue
>> (http://bugs.php.net/bug.php?id=42526). You can't claim that locale
>> insensitive tolower() breaks things, because your functions are locale
>> insensitive in some setups.
>>
>> Now I can only see that PHP developers close bug reports as "bogus" or
>> "won't fix" without any good explanation. I think I've already said on
>> this list once. If you lie in order to prove your point, you lose. You
>> don't need PHP6 in order to fix it. Fix is possible or I don't see whole
>> picture.
>>
>> --
>> Tomas