Richards-san wrote:
> >[...] where they had made a nice method to change the language
> > of the screens, but all the input field validation were based on American
> > standard. Not very smart.
I've used a number of such pages where I was unable to enter a valid phone
numbers and/or zip code due to such server-side checks.
> Things to note like this, in Australia we call them postcode, and have four
> digits, in England they have letters and numbers.
And in Japan it's ###, ###-##, or ###-####. While the 3-4 version is the
"official" one now, the others get the mail there still. It's like just
using the 5-digit version in the U.S.
> We have 8 digit local
> phone numbers (everywhere else has 6 or 7 I think and a 3 digit area code).
This is a tough one in Japan. The area code always begins with 0 (unless
calling form outside of Japan) and may have 1,2, or 3 digits afterword. The
next part could be 2, 3, or 4 digits depending on the size of the "area."
Then the last part is always 4 digits. And, no, they don't always add up to
the same number of digits overall. I think that keitai (cellular) phones are
all now 12 digits, with a given 4 digit "area code" given to each service
provider. (Don't quote me on that one, though, as I'm still holding out on
being on call 7/24, so don't quite know all the facts.)
Also, there was something about currency mentioned. When localizing for
currency, wouldn't some sort of logic have to be added to convert from a base
currency to the one of the locale? Geneally, when I purchase something over
the Internet from a foreign country, it's in the currency of that country.
So I don't understand why this would be a feature of the presentation section
and not be part of the back-end logic (separate from Struts). I think I
would need an example before I could comment any further on the merrit of
this one.
--
Michael Westbay
Work: Beacon-IT http://www.beacon-it.co.jp/
Home: http://www.seaple.icc.ne.jp/~westbay
Commentary: http://www.japanesebaseball.com/
