I do some part-time work at a non-profit that, ultimately, does super-international (30+ countries) surveys. As you might imagine, this results in a massive database and my main duty is wrangling the data into a .csv-friendly format.
One of the quick things we learned that "normalization" in the naive sense was an exercise in idiocy.
Breaking names into 'first name' and 'last name'? Hah, right.
Breaking locations into 'country', 'state', and 'city'? Hah, right.
The big solution: don't constrain what someone types in. Constrain how you work with it.
Funny that I hit this all the time with Japanese services online. Enter First Name in latin characters: "sorry, invalid characters" ... enter in full width latin characters .. "sorry, invalid characters"
I've even encountered sites which only allow hiragana for names - won't even accept katakana!
Until patio11 amends this post to contain suggestions about doing things right instead of merely telling people that they are doing it wrong, please stop recommending it as reading material. Thanks.
I remember signing up to websites in the late 90s that hadn't quite grokked internationalization. "Select your country (required)" , "United Kingdom" , "select your state (required)".
Apparently there is such a thing as Alabama , England. Who knew?
The first name and last name thing annoys me the most. I can't use my real name in most online services (yes, Facebook and Google, I am not using my real name, coz I can't!), because my official name is a mononym. When registering for PayPal, I had to sent at least 10 emails to get someone to respond to be able to use my real name for transactions.
One of the quick things we learned that "normalization" in the naive sense was an exercise in idiocy.
Breaking names into 'first name' and 'last name'? Hah, right.
Breaking locations into 'country', 'state', and 'city'? Hah, right.
The big solution: don't constrain what someone types in. Constrain how you work with it.