I agree here with Glen. I have never seen in my time in IBM where debug trace was I18N. I have also worked overseas and for technical positions it was understood that English was a requirement. I even once asked some of the developers at the time why they didn't get product documentation in their native language and was told that technical translations were so poor that it was almost useless. Besides the trace information is for the most part useless unless you have a reasonable understanding of the code in which case as part of the translation effort will the code comments be also translated? :-) It also adds additional cumbersome when trying to debug to have to look up in message tables to match the trace statements with the outputs. Which also leads to developers ultimately not putting trace statements in whatsoever.
>I don't agree (obviously, since I keep i18ning them!). IBM's got customer >support sites all over the world. Most of the problems they support will >be resolved by them and not even get to a developer back here. When they >tell their customers to turn on debug, they would really prefer to work in >their own language. >Russell Butek >[EMAIL PROTECTED] > >Glen Daniels <[EMAIL PROTECTED]> on 03/14/2002 10:16:30 PM >Please respond to [EMAIL PROTECTED] >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >cc: >Subject: RE: cvs commit: xml-axis/java/src/org/apache/axis/wsdl/toJava >Jav aComplexTypeWriter.java JavaStubWriter.java > > >You know, if you ask me, it's going a bit far to internationalize debugging >trace messages.... > Rick Rineholt "The truth is out there... All you need is a better search engine!" [EMAIL PROTECTED]
