Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79366
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.220.49 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <5476DF5C.6040807@gmail.com>
References: <CAESVnVpkEmCxL-hApFX=iidA+J3Aejw7ryDs1FjomUSkymQpNA@mail.gmail.com>
	<54767CAC.9060608@gmail.com>
	<5476DF5C.6040807@gmail.com>
Date: Mon, 1 Dec 2014 17:23:20 -0800
Message-ID: <CAESVnVpmNhx=RdZmED7Gmqhy+h35j8jdgigCqMU2_AYZNA936A@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] IntlChar class and intl_char_*() functions
From: pollita@php.net (Sara Golemon)

On Thu, Nov 27, 2014 at 12:22 AM, Stanislav Malyshev
<smalyshev@gmail.com> wrote:
> Looking into this and also reading the \u{} proposal, I also thought -
> do we have a programmatic way of doing what \u would do? I.e. if we
> assume $x holds an Unicode codepoint value (i.e., an integer) do we have
> a good built-in way to generate the corresponding utf8 sequence?
> If not, then I think this class may be a good place to put such a
> function in.
>
Yeah, that's some of what this class and/or set of functions would
expose.  Numeric codepoint to utf8 sequence, codepoint name (e.g.
"LATIN CAPITAL LETTER P") to utf8 sequence, numeric codepoint to
codepoint name, utf8 sequence to numeric codepoint, etc...

At this point I haven't heard any major directions so I'm going to
start work on implementing it so that we have a more firm base to
discuss and we can continue once I have that up for review.

-Sara