Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78093
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
Message-ID: <543E4626.3000102@gmail.com>
Date: Wed, 15 Oct 2014 13:02:14 +0300
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Rowan Collins <rowan.collins@gmail.com>, internals@lists.php.net
References: <543CE705.7030203@gmail.com> <4575A816-43F4-462D-8150-A2D35516D914@ajf.me> <543D64E5.8000706@gmail.com> <543D8528.1060605@gmail.com> <543D8FFA.8080408@gmail.com> <543DAA29.8040701@gmail.com> <68E97150-8840-4C31-B271-3E8C8BE933DB@gmail.com>
In-Reply-To: <68E97150-8840-4C31-B271-3E8C8BE933DB@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Unicode support
From: aleksey.tulinov@gmail.com (Aleksey Tulinov)

On 15/10/14 10:04, Rowan Collins wrote:

Rowan,

> As I said at the top of my first post, the important thing is to capture
> what those requirements actually are. Just as you'd choose what array
> functions were needed if you were adding "array support" to a language.
>

I'm sorry for not making myself clear. What i'm essentially saying is 
that i think "noël" test is synthetic and impractical, it's also 
solvable with requirement of NFC strings at input and this is not 
implementation defect. I also believe that Hangul is most likely to be 
precomposed and will work alright. And i have another opinion on UTF-8 
shortest-form.

This is my personal opinion of course.

That aside.

I think requirements is what i was asking about, i'm assuming that your 
standpoint is that string modification routines are at least required to 
take into account entire characters, not only code points. Am i correct?

What is confusing me is that i think you're seeing it as a major 
implementation defect. To avoid arguable implementations, i've made 
short example in Java:

System.out.println(new StringBuffer("noël").reverse().toString());

It does produce string "l̈eon" as i would expect. Precomposed "noël" also 
works as i would expect producing string "lëon". What do you think, is 
this implementation issue or solely requirements issue?