Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47220 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35853 invoked from network); 13 Mar 2010 14:05:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Mar 2010 14:05:10 -0000 Authentication-Results: pb1.pair.com header.from=mozo@mozo.jp; sender-id=permerror Authentication-Results: pb1.pair.com smtp.mail=mozo@mozo.jp; spf=permerror; sender-id=permerror Received-SPF: error (pb1.pair.com: domain mozo.jp from 209.85.212.42 cause and error) X-PHP-List-Original-Sender: mozo@mozo.jp X-Host-Fingerprint: 209.85.212.42 mail-vw0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:60745] helo=mail-vw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2D/A2-15916-49B9B9B4 for ; Sat, 13 Mar 2010 09:05:10 -0500 Received: by vws18 with SMTP id 18so186989vws.29 for ; Sat, 13 Mar 2010 06:05:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.128.16 with SMTP id i16mr266363vcs.0.1268489106200; Sat, 13 Mar 2010 06:05:06 -0800 (PST) In-Reply-To: <4B9B7260.1000205@lsces.co.uk> References: <4B9926E8.4080202@lerdorf.com> <7f3ed2c31003120958w7bd41059o88869669c6f5b0d9@mail.gmail.com> <661d85d51003130107o7cf19012m7ce93f0147c7585a@mail.gmail.com> <4B9B7260.1000205@lsces.co.uk> Date: Sat, 13 Mar 2010 23:04:46 +0900 Message-ID: To: Lester Caine Cc: PHP Developers Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] PHP 6 From: mozo@mozo.jp (Moriyoshi Koizumi) On Sat, Mar 13, 2010 at 8:09 PM, Lester Caine wrote: > Handling unicode CONTENT is not the problem here. People nowadays expect to > be able to use their own language to write code, and create functions using > words that they recognize. In databases, table and field names are now > expected to support unicode, rather than just handling unicode data pumped > into ascii titled fields. > > Personally I'm quite happy with just using ascii names for things, but more > and more overseas customers provide contact details in 'strange' character > sets that only unicode can handle, and handling THAT in PHP5 is not a > problem. It's when people start building databases with unicode metadata and > expect the tools interfacing with that to understand unicode as well. > > It was my understanding that PHP6 was intended to provide international > users with something that they could use in their own native language? > Unicode titled files with unicode titled classes and functions. I doubt that many people are gonna start using non-latin characters for the identifiers, as long as most of those generally use the alphabetic keyboard, with which I cannot type any Japanese words as fast as alphanumerics. In addition, I think RTL languages such as Arabic aren't supposed to use with latin punctuation marks in a programming language in the first place. Moriyoshi