On Jun 26, 2006, at 8:39 AM, Sean Coates wrote:
I can just cvs remove the existing files and re-add them with their
lowercase names, but this will lose the history information
attached to
the files? Is there another way you recommend I handle this?
This will upset translators. (-:
I can move the files in CVS.
Translators: will that work for you?
I was about to make this change, but stopped.
I came to the conclusion that the proverbial uppercasefilename cat
is is
out of the bag.
[EMAIL PROTECTED]:~/php/cvs/phpdoc/en$ find . | egrep "[A-Z]" | grep -v
CVS | wc -l
572
Meaning? There are ~572 files that need to be renamed -- and that's
only
in the en/ tree. No thanks.
Let's not pick on Ben and SimpleXML (-:
There appears to be 356 (ignoring ZEND and internals) that need
changed (in en/), but that number also looks too high!
I think it's fine to pick on ben and simplexml here :), this is a
newish extension that should adhere to our guidelines despite a
history that fully did not. We should at least fix this extension.
And xmlreader.
Culprit extensions: domxml, ming, oci8, pdo*, sdo*, simplexml, spl,
tidy, xmlreader
So we need to reevaluate our rules here especially how they relate to
OOP extensions. How about we add that to the TODO and after some
thoughts come back to this topic.
Regards,
Philip
