Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16425 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69150 invoked by uid 1010); 6 Jun 2005 12:24:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 69134 invoked from network); 6 Jun 2005 12:24:03 -0000 Received: from unknown (HELO osu1.php.net) (127.0.0.1) by localhost with SMTP; 6 Jun 2005 12:24:03 -0000 X-Host-Fingerprint: 62.58.68.2 firewall.axit.nl Received: from ([62.58.68.2:19298] helo=localhost.localdomain) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id 26/AE-53949-16044A24 for ; Mon, 06 Jun 2005 08:24:01 -0400 Message-ID: <26.AE.53949.16044A24@pb1.pair.com> To: internals@lists.php.net References: <8D.C1.12345.13F50A24@pb1.pair.com> Date: Mon, 6 Jun 2005 14:23:52 +0200 Lines: 35 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Posted-By: 62.58.68.2 Subject: Re: Proposal for Implementing Unicode in PHP From: r.korving@xit.nl ("Ron Korving") I couldn't agree with you more. This would be a great new feature for PHP 5.1 (which it probably won't be), or 5.2. Ron "Steven Wittens" schreef in bericht news:8D.C1.12345.13F50A24@pb1.pair.com... > Hi, > > As a PHP user I'm sadly confronted daily with PHP's lack of proper > Unicode support. PHP is rapidly falling behind the competition... as far > as I know, Perl, Python, VBScript, Ruby all have good Unicode > implementations. That PHP still doesn't have that after so many years > sounds like there is a general lack of awareness about the issue from > the core team and what to do about it. > > I'm not a big shot C coder, but I do know a lot about encodings and > Unicode, so I've outlined the big "Unicode and PHP" problem in an > article, along with a proposal on how to tackle it: > > http://www.acko.net/blog/unicode-in-php > > It's a bit long, but then it's a complicated issue. I hope you guys find > it informative or at least skim over the bold parts to see what is > causing me and many others to tear my hair out in frustration and > seriously consider alternatives. > > Thanks, > Steven Wittens > > PS: Sorry if this has to go to PHP-I18N instead, but that list seems to > be aimed at practical I18N problems.. not fundamental changes in the > core. Internals seemed more appropriate for this.