Hi Joe and Rowan, On Mon, Mar 2, 2015 at 6:37 AM, Rowan Collins <rowan.coll...@gmail.com> wrote:
> On 01/03/2015 20:34, Lester Caine wrote: > >> On 28/02/15 06:48, Joe Watkins wrote: >> >>> This is just a quick note to announce my intention to ready this RFC >>> for voting next week. >>> >> Since there is nothing in this which needs any changes to the core then >> surly it simply needs to exist in pecl until such time as a proper >> replacement for unicode in core strings has been addressed? Since it >> will still require intl to provide those areas it does not support, and >> I question if we really need to provide yet another encoding converter. >> >> A unicode string handler that just handles UTF8 strings may be yet >> another stepping stone, but it still falls short of beings able to >> handle all of the internationalization problems and is simply an >> alternate to mbstring so one either runs both, or sit down and convert >> all the third party libraries to eliminate mbstring. >> >> Like http extension, it's not essential that it's loaded by default, and >> leaving it in pecl allows development outside that of the core? >> >> > I think this is probably a good idea at this stage. It will give people a > chance to play around with it in an "experimental" state before committing > to maintaining a particular API. > > Since there's no real BC break here, there's no reason it couldn't be > bundled into 7.1 if it was deemed ready by then, so it seems unwise to rush > into including it in 7.0 straight from what feels like a prototype > implementation. Sounds reasonable. Joe, I don't have much time to help, but I'm willing to help UString development. I think it's better to keep it simple. Having unified internal encoding (NFC normalized UTF-8 string without BOM) for internal string representation would be much simpler than multiple encodings. We may consider various issues/ideas like this in relatively long term. http://websec.github.io/unicode-security-guide/character-transformations/ http://docs.parrot.org/parrot/latest/html/docs/pdds/pdd28_strings.pod.html Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
