Perhaps you could provide an example or two on "how to document a
unicode change" as currently I for one would not know where to begin.
Like the best way to go about finding [1] and documenting a unicode
related change. And an estimate on about how many functions will
eventually require documentation changes for this. 50, 200, 500, 1000,
...?
The only reliable way is to read the source code, of course. :) But
seriously, it might be tough for someone to pinpoint what
Unicode-related changes have been done to a function. As an example,
the notes for strtoupper() and strtolower() could say something like:
These functions perform full case-mapping according to the Unicode
standard [1]. Consequently, the length of the string may not be the
same after the operation: it may become shorter or longer.
[1] http://www.unicode.org/versions/Unicode4.0.0/ch05.pdf#G21180
As for how many functions will require documentation changes, it's hard
to say, as we've only upgraded about 200 right now. I would say that
about half of the string funcs may require some notes.
Also, the doc team is sort of on vacation currently but once Livedocs
[3] is online I have a feeling we'll make a concerted effort to
attract additional help on all fronts.
Makes sense.
-Andrei
