Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47232
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mozo.jp from 74.125.92.25 cause and error)
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.00.1003131123540.4153@kossu.derickrethans.nl>
References: <4B9926E8.4080202@lerdorf.com> <alpine.DEB.2.00.1003131123540.4153@kossu.derickrethans.nl>
Date: Sun, 14 Mar 2010 02:38:50 +0900
Message-ID: <cd1fb7541003130938p1d1dced7nc45c190c08fd61ce@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Rasmus Lerdorf <rasmus@lerdorf.com>, 
	PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] PHP 6
From: mozo@mozo.jp (Moriyoshi Koizumi)

On Sun, Mar 14, 2010 at 1:57 AM, Derick Rethans <derick@php.net> wrote:

> - in the meanwhile, start working on patching in back Unicode support,
> =A0but in small steps. Exactly which things, and how we'd have to find
> =A0out. But I do think it needs to be a *core* language feature, and not
> =A0simply solved by extensions. We also need to make sure everybody
> =A0understands that Unicode isn't just about encodings, or charsets and
> =A0that thre are differences between that. Education is going to be
> =A0important (and adding Unicode back in small bits would certainly help
> =A0there).

Unicode isn't just about a coded character set, but a whole lot of
specifications that are essential in handling various kinds of texts
within an application.  But, I don't really think it reinforces the
reason Unicode functionality needs to be part of core language.

Moriyoshi