- gettext - tough to do without it. The messages are essential to the
end user. Without it they either a) end up with the send
errors/status only in english or b) each implementation would have to
jump hoops to get them localised. I'm using these in Italy so I've
seen the significance of getting back meaningful localised messages
to the end user. It can always be overcome by including a dummy
gettext function for those that don't have it, and resulting in
english only messages.
gettext is a big hastle sometimes, - I've had servers where it wasnt installed, let alone the problems setting it up to actually work..
One of the main big projects I did a while ago, used a Simple PHP NET_SMS solution on an embedded box (connected to a vending machine and wireless modem, to dial in sales data) - and I can tell you for sure, that didnt need/have gettext :)
From my reading of PEAR_ErrorStack, it has support for error messages with arguments (which where designed for translating AFAIK), - it may be worth thinking about using that instead of PEAR_Error.
Can you help out?
Need Consulting Services or Know of a Job?
http://www.akbkhome.com