Michael McAngus wrote: >> I don't know what you refer to when you say "most of the rest of the >> world," and "western bigotry."
What I meant, no offense intended, is that in my experience, it is American developers who have the least tolerance for the internationalization and localization concerns of application development. They bring a "my locale is the only valid locale" attitude to their work. For more than 8 years I worked at a company where we developed and shipped several applications (AIX, X/Motif) simultaneously in 6 languages (English, French, Spanish, German, Italian, Japanese). During that period, the foreign developers I worked with (primarily French) and foreign marketing execs displayed a greater tolerance for localization variety while American developers, engineers, and others quite frequently had a "that's stupid because we don't do it that way here" mentality when dealing with such concerns. That mentality frequently led to code which blatantly ignored i18n issues in favor of an en-US specific implementation. >> The code I submitted defaults to the comma, and it uses only the decimal >> separators that are returned by java.text.DecimalFormatSymbols >> (currently comma and period). OK. And is that configurable so that one can choose the separator independent of current locale? Jim <font size="1">Confidentiality Warning: This e-mail contains information intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, any dissemination, publication or copying of this e-mail is strictly prohibited. The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this e-mail. If you have received this e-mail in error, please immediately notify us by return e-mail. Thank you.
