other languages
| From: | Lukas Smith | Date: | Mon, 01 Aug 2005 12:45:31 +0000 |
| Subject: | other languages | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-39079@lists.php.net to get a copy of this message | ||
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).
Another thing that would need to happen is to make it easier for the user to provide a code to text mapping and then have the classes transparently use that instead. While all of my packages try to make use of codes I dont have anything in place for that. As a matter of fact I usually statically define the mapping inside a method.
I dont think we need to start making this stuff a requirement, but it might be sensible to ponder about the issue and come up with a somewhat standard recommended approach in PEAR.
regards,
Lukas