> And, most importantly, what the hell doi I care of losing 0.000012 secs > for a Fatal Error dysplay?
I don't like the whole idea of having localized error messages. People have to use English when programming PHP anyway, and nobody is insane enough (yet) to suggest to translate function names. I don't think "Parse error" is any more difficult to understand than register_shutdown_function(). People use manual for understanding things like this. And I do care about unnecessary performance loss. But most of all I care about maintenance nightmare that this localization would put us in. If some of the pro-localization ever bother to read the php-bugs you would know that even a simple matter of using the correct .ini or .dll file can be too much for your target audience. Adding some CDB file to it is not going to help. The other side is maintaining the translation in the PHP code itself. This is just too large a task for the current team. I think it would be far more useful that some energy is spent on keeping PHP manual up to date so say our Italian users would have some clue about streams once PHP 4.3.0 hits the street. Edin -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
