[prev in list] [next in list] [prev in thread] [next in thread] 

List:       php-internals
Subject:    [PHP-DEV] Wiki-page for unicode status and ideas
From:       Jacob Oettinger <jacob () oettinger ! dk>
Date:       2010-03-31 23:13:09
Message-ID: D8004CBE-BE36-480D-ADE4-56D7992CC95E () oettinger ! dk
[Download RAW message or body]

Hi
David Zülke kindly let me know that I mis-posted the message below by posting it as a \
reply with a different subject. So here it is again, now in its own thread. (sorry \
about the double post)

Hi all,
I have been following the internals list since I heard that the unicode effort had \
grinded to a halt (so I am quite the noob into the php internals world).

I have some ideas for possible ways to implement unicode handling. My guess is that \
most of these have been discussed earlier but I do not seem to be able to find any \
good way of reading up on the choices that led to the php 6 unicode implementation \
(please direct me in the right direction if such a source is available). It would \
also be great if there was a source of information that listed some of the caveats of \
the project that I am guessing is what is making it hard to implement.

I proppose that we make a wiki page that attempts to summarize information about \
unicode support in php. Some of the headlines on the page could be:

* Desired features
* Cavets
* The "php 6 way"
* Possible alternative "ways"

I think this would give a good overview that would make it easier to make the right \
decision on how to move forward.

I would like to organize/collect/manage the information, but I need help in finding \
the needed information.

Is this a good idea?
Is it silly to have someone, that has not been involved in the earlier unicode \
discussions, trying to summarize on them?

Regards, Jacob Oettinger
-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php


[prev in list] [next in list] [prev in thread] [next in thread]