Re: Re: other languages

Hey g&g ! Pierre-Alain Joye wrote:

On Mon, 01 Aug 2005 14:45:31 +0200 lsmith@php.net (Lukas Smith) wrote:

Hi, Quite sensibly PEAR uses english as its base language. However here (http://www.pear-forum.de/viewtopic.php?p=2464#2464) is a post on a german forum that raises an interesting and important issue: PEAR provides no proper way for developer to display error, status and other messages in a translated form. I raised this on IRC and one solution that was proposed was gettext. However gettext is painful in alot of ways. Most importantly messages will likely get minor modifications and using gettext this would become a BC break. The best solution IMHO is using error, status etc codes. Especially for error codes this means once again extending from PEAR_Error (otherwise it would be impossible to determine what error code map to use for a given error object).

Error codes sound good (textual or numeric). I do not see a point to allow localized errors. Except 4d (which translates its langage too), I do not know any other with such custom errors. Errors codes are the only way , in the sense pear delivers general extensions and we cannot quite decide if the message has to be seen and how.

(what does not means we shouldn't deliver a standard english for it) However, codes can be number or other, they should be represented by meaningfull constants. But please ! Code must be specific to a package. Did none of you experienced error code messing issued from packages using both the peculiar 1,2,3,... ? If code, not 2 packages should be able to have the same. à+ -- bertrand "toggg" Gugger