Date: 12/20/00
- Next message: vitaliyf <email protected>: "[PHP-DEV] PHP 4.0 Bug #8328: ucwords and ucfirst misbehaving with quotes"
- Previous message: Andi Gutmans: "Re: [PHP-DEV] RE: [PHP-QA] Re:RC6 ISAPI problems"
- Next in thread: Sascha Schumann: "Re: [PHP-DEV] Translating PHP error messages (fwd)"
- Reply: Sascha Schumann: "Re: [PHP-DEV] Translating PHP error messages (fwd)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I personally don't like multi-lingual support. I think software developers
all over the world pretty much have to learn English in order to get around
so I think they can handle English PHP error messages. It also makes it
harder for us to debug if they send us foreign language error messages.
We'll need to cross reference them (with an error#) which is yet another
step to not replying right away but having to go and open a file. Sucky IMO.
Andi
At 12:23 PM 12/19/00 -0800, Rasmus Lerdorf wrote:
>I think this is a worthwhile thing to pursue. If we do it at compile-time
>as suggested then we won't have any performance issues. I think a
>run-time solution might be more useful though although it would be a bit
>slower. Speed of printing errors and warnings isn't really critical.
>
>-Rasmus
>
>---------- Forwarded message ----------
>Date: Tue, 19 Dec 2000 19:42:02 +0100
>From: Damien Seguy <dams <email protected>>
>To: rasmus <email protected>, bibi <email protected>
>Subject: Translating PHP error messages
>
>Hi Rasmus,
>
>I have noticed that all the error messages are in English.
>I think it could be interesting for all to be able to build a PHP version
>with localized error messages.
>
>This is the way I was thinking to build it:
>
>1. For every php_error() function call, replace the second argument (which
>is a
>constant) with a #define
>2. Gather all #define statements in one file called <langage>.h somewhere (I
>really dont know where to put those files)
>3. Add a compilation directive (something like --lang=<langage>) to let the
>user choose the langage he wants
>
>
>I know this is a huge work (I've counted 1739 distincts call to php_error)
>to
>go through every files to modify the php_error() function calls. With little
>effort,
>PHP will become more user-friendly and speak in everyone's own language.
>
>So let me know what you are thinking about this project, or if it is already
>started.
>I also wonder who (where) is the best to be asked for. I understand that PHP
>is a
>community effort, I'd like to take my share, but without pissing everyone
>off.
>
>Can you help me help you?
>
>Best regards
>Ghislain and Damien Seguy.
>http://www.nexen.net/
>
>
>
>--
>PHP Development Mailing List <http://www.php.net/>
>To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
>For additional commands, e-mail: php-dev-help <email protected>
>To contact the list administrators, e-mail: php-list-admin <email protected>
--- Andi Gutmans <andi <email protected>> http://www.zend.com/-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: vitaliyf <email protected>: "[PHP-DEV] PHP 4.0 Bug #8328: ucwords and ucfirst misbehaving with quotes"
- Previous message: Andi Gutmans: "Re: [PHP-DEV] RE: [PHP-QA] Re:RC6 ISAPI problems"
- Next in thread: Sascha Schumann: "Re: [PHP-DEV] Translating PHP error messages (fwd)"
- Reply: Sascha Schumann: "Re: [PHP-DEV] Translating PHP error messages (fwd)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

