Husted-san wrote:
> The validation.xml supports creating FormSets for different locales.
Wait a second. You just said "locales" right? Yet what are Java locales
used for? Language.
I live in Japan, however, if I'm browsing in English, what kind of phone
number am I going to get? Dose the web designer need to write a en_JP
locale? How about Spanish speakers in California?
The name "locale" has always bothered me with Java, because it tends to be
used to define a language rather than a place. Yes, there are en_UK and
en_US versions, but even those are for differences in language expressions
more than location.
Now, let's say that my wife, born in Mexico, raised in the U.S., and now
living in Japan, is surfing the Web in Spanish, and wants to send a present
to a friend in Brazil. She's asked to enter a zip code. What "locale" will
be presented to her?
Perhaps I missed something somewhere along the line where "locale" was
differentiated from "language" resources. It's probably just a semantics
problem as you all have probably been thinking all along that the checks are
to be done based on the country that the user enters in a form, not the
"locale" to which (s)he is surfing. But that'll be something else that one
must keep in mind when solidifying a spec.
Sorry, but even though "locale" is probably the correct word here, it's kind
of confusing in the context of i18n in Java.
--
Michael Westbay
Work: Beacon-IT http://www.beacon-it.co.jp/
Home: http://www.seaple.icc.ne.jp/~westbay
Commentary: http://www.japanesebaseball.com/
