Re: New flame
| From: | Lukas Kahwe Smith | Date: | Tue, 24 Jun 2008 14:20:24 +0000 |
| Subject: | Re: New flame | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-38575@lists.php.net to get a copy of this message | ||
On 24.06.2008, at 16:10, Derick Rethans wrote:
On Mon, 16 Jun 2008, Andi Gutmans wrote:At this point there is no 1st hand user known. There is no example code. At the same time a lot of core developers question if the code is even able to work in any reliable and secure way. Finally the feature is not even documented. As such the conclusion can only be that investing any time in readding this "feature" would be a bad idea. If anyone actually uses this feature they will have to come out of the woodwork now or when 5.3 is out. At this point we might have enough information to actually understand how that feature is used and how we can add it to 5.3. regards, Lukas Kahwe Smith mls@pooteeweet.orgI've asked around a bit as well with our customers/partners, and all they seem to answer is "we simply use UTF-8".From: Lukas Kahwe Smith [mailto:mls@pooteeweet.org]This is used when reading scripts that are in encodings like Shift-JIS which is very common in Japan. In any case, I have tried to get involvement from some people I know over there without much success.I was under impression parser multibyte support wasn't yet fixed. Was it?Maybe we should decide if this a show stopper or not. From my understanding we still do not have any example of this being used in the wild ..