> > > On Mon, 25 Nov 2002 15:21:06 -0500 Sterling Hughes <[EMAIL PROTECTED]> wrote: > > > Educate users to speak the base amount of english required, I18N'ing the > > language is just going to lead to headaches from a user perspective > > (incorrect translations, slower performance, translations for english speakers) > > and a developer perspective (having to lookup tokens, understanding another > > language, getting bug reports with horrible error messages). > > That is why we have error codes :) >
Bull, that's why we don't obfusticate :) > Are you saying that Oracle is wrong giving the ability to localize even > SQL error messages? These does not have to ever happen, but in my > Italian team the guys are simply rocking - they find out instantly what > they did wrong to a query because it is in their language. > Kinda funny, This summer I worked w/ Oracle in German, I survived. Same for SAP.... I spent about 15 minutes to learn the terms, and was set, besides using the german terms when all the german SAP consultants used the English terms (bedarfsbestandliste, stammdaten, lallalaa). If there was an error, I asked a colleague or looked it up on the internet - I survived. This happens to tons of php developers across the world, its not really that hard, and it really does open up pandora's box, also from an implementation perspective, its alot more feasible for Oracle than for PHP... -Sterling -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
