I would suggest changing the terminology here. A "string" is quite
simply an array of bytes, with no intrinsic meaning or encoding. This
"UString" is something quite different, and giving it a similar name
might cause confusion. I'd suggest calling it a "text" type.
Having distinct "string" and "text" types would aid in reminding people
that strings are not, in fact, text, a fact which it can be difficult to
grasp.
But perhaps that makes sense only to me.
On 31/08/12 13:20, Ferenc Kovacs wrote:
My modest proposal to provide Unicode support to PHP without the need to
>>rewrite the whole engine and its libraries introducing the UString
>>abstraction
>>layer as a regular class, an with minimal support from the core engine.
>>Basically, the UString class hides the internal implementation of the
>>Unicode
>>strings and allows to experiment with several solutions (UTF-8, UCS-2,
>>UCS-4,
>>...).
--
PHP Unicode & I18N Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
