>Agreed. That is precisely what Kerry recommended, and precisely what I
>intend to do.
There's a good reason to give the user the option (Bruce already knows
this, but it's a little localization tidbit for some of us).
First, a little background for those who aren't into localization. If
you're going to sell a product in Spain, it obviously should be in Spanish.
That's just the language, though. There's another factor we localization
people have to consider--the locale. In fact, let's capitalize that--the
Locale.
Spanish is spoken in Europe, South America, Central America, and large
parts of North America. As you might guess, usage and vocabulary varies
widely from region to region.
Other things differ by Locale--time and date formats, number formats, and
so on.
It's easy to get the Locale when you're using C++. Every localization
engineer knows that to properly localize a product, you have to have the
Language and the Locale.
It's too bad Director doesn't have a way to easily detect the locale. I'm
going to add it to the wish list.
Now, the original point--why should it be a user configuration item? Even
if you can get the Language and Locale from the system settings, how do you
accommodate the Italian, French, and Portuguese Siemens employees who are
in Germany for a conference? You can't force them all into German--you
should give them a choice.
Cordially,
Kerry Thompson
Learning Network
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
