Fair enough. I will propose a question to the list.
My current idea is that the Unicode-related functions should be
documented separately from the i18n functions. Your list (
http://philipolson.gotdns.org/unicode-file-list.txt ) doesn't seem
complete, though: where is unicode-encode.xml ?
In any case, from that list, everything starting with collator* or
locale* should be in i18n section and the rest - in Unicode section.
We also need a top-level section where we give intro to Unicode, how it
works in PHP, new string types, operators, etc.
-Andrei
On Feb 6, 2007, at 11:42 AM, Philip Olson wrote:
We could do a split on the unicode/i18n border. I think i18n will
mainly be done in a new ext/icu extension. Everything that's in
ext/unicode or in the core, should be documented together. The
exception might be the collator, but we can talk about that.
Just a fyi, before I do anything to ref.unicode you will need to
either draw a clear line, by function, or you propose the question to
the list with thoughts on the matter. In other words, I have no idea
what to do so plan to do nothing at this point. The script produces 86
functions for ref.unicode. I think to move forward either you or Sara
will need to be active on the doc mailing list (and/or #php.doc) at
least for awhile. I don't mean to sound demanding, but rather, just
want to be honest and tell you where I'm at. I look forward to helping
make this happen!
Regards,
Philip
