As far as I have seen adding an entity was the suggested method, which
should not be a problem for translators to adapt to IMHO. In case this
entity is just a "this has unicode support" text, and nothing more, and if
all text handling functions will indeed have Unicode support, then adding
these entities is really not seem to worth it.
Gabor
The problem is: thats not only the text handling functions.. we are talking
about all functions! I don't remember how many they are, but they are many.
Fine, but what I was saying is that the behaviour of number of functions
will change, slightly or more than slightly, depending on unicode
semantics mode being on or on the type of data passed to them. Those
changes need to be documented.
-Andrei
Ah sure! Some protos may need changes, and some functions may need tweaking,
of course. But all this will need to be made manually and thus will take a
long time..
I think we can start by describing the general behaviour of the extension on
the reference.xml page and then, as time permits, touch the function pages.
Nuno
- Re: [PHP-DOC] Starting on Unicode docs Nuno Lopes
-
