> I think a split is a good idea though I think a name change could be > confusing (don't know if that's what you're suggesting?). A lot of web > developers probably considers themselves PHP developers and will > go to "PHP Developers manual" even though they're looking for > information which is in the other manual. (Just like the php-dev list > receives e-mails from users asking about development _in_ php.)
Well, I know about this "PHP Developer" problem... While this is not a problem for eg. MySQL, where it's clear who is a user and a developer, it's not that simple for PHP... Maybe we can leave the PHP Manual as it is know and just name that new manual with a good title, such as "PHP Inner Workings Manual" or something like that just to avoid confusion... Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
