by Michael S. Kaplan, published on 2006/03/01 11:01 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/03/01/541309.aspx
I am not sure when it started or by who, but there is a popular expression "Math is hard, let's go shopping!" that is perhaps best captured in the generic form "* is hard, let's go shopping!"
I believe the closest thing to a Language Log analysis is this post, so clearly there is work to be done....
Anyway, think of today's title as an homage to this particular phrase, which has been co-opted by various people on the GIFT team (perhaps the funniest use I have personally witnessed was "Shopping is hard, let's go sho-... um... never mind!"). And today's post is dedicated to fellow GIFT-ers Mike, Cathy, Kieran, and everyone else who has enjoyed using it. :-)
The other day Anutthara commented:
Hi Mike - it is interesting to note that the settings support for different locales is limited to date, time, currency and numbers and very minimal string based stuff (if you consider the date manipulation as string based i.e.) Now, we know that addresses and even names are represented differently in different countries like (FirstName, LastName or LastName, FirstName or FirstName.MiddleName.LastName) Is there any reason why these settings are not specific per a defined locale? I am sure apps like One Note or Outlook would require these settings. Is there an API to set/get this kind of format?
(the comment is unrelated to the post to which it was attached)
It is an excellent question that is often asked.
The problem is that it is improbable bordering on impossible to accurately capture the per-locale differences in address formats because there are so many possible differences.
I captured a sampling in my book and both v1 and v2 of Developing International Software did the same, but even these snapshots have many limitations in trying to capture the vast array of differences.
Outlook actually does attempt to do this sort of thing and has even offered up their data to NLS in the past as a "great way" for the OS to support this feature, but their actual support is incomplete and the limitations with the data simply do not meet the quality bar and leave the data as being little more than a starting point on the road to such a feature, without clear info on how best to capture the information for users.
Aside: interestingly, there is a thread going on right now in the NewsML 2 list about attempting to capture in a standard the differences in people's names. This effort, predictably enough, suffers from the problem that the late James Doohan aptly described in the third Star Trek movie -- "the more they overthink the plumbing, the easier it is to stop up the drain."
Whether the exact overthinking is in the NMTOKENS structure or the hugw number of attributes (family, rendition, pronounce, last, given, middle, nickname, baptismal, and so on), or in the extensive discussion on whether to use IPA for the pronunciation or not, I think this is destined to be yet another very complete and also very unused standard for capturing peoples' names across cultures.....
Now ignoring this latest [over-]development on the naming front, this is a problem that is worthy of a solution, though being worthy of a solution does not really get things solved, especially as an OS service (where email address are about 10000 times more likely to be useful). Even in Outlook it is a stretch as a required feature (though Exchange tries hard to support the many names in its addressbook features!), although the potental usefulness in Word for mail merge is undeniable (and also not really present there).
The generic issue brought up by Anutthara about the "simple" nature of the existing locale data is one that I plan to talk about tomorrow. :-)
This post brought to you by "དྷ" (U+0f52, TIBETAN LETTER DHA)
# Nick Lamb on 1 Mar 2006 12:54 PM:
# Jason on 1 Mar 2006 1:14 PM:
# Michael S. Kaplan on 1 Mar 2006 1:17 PM:
# Michael S. Kaplan on 1 Mar 2006 1:18 PM:
# Shoshannah Forbes on 2 Mar 2006 10:34 AM:
# aside on 2 Mar 2006 1:29 PM:
# Michael S. Kaplan on 2 Mar 2006 1:56 PM:
# Liz on 2 Mar 2006 4:18 PM:
# Anutthara MSFT on 3 Mar 2006 1:26 AM:
Michael S. Kaplan on 8 Apr 2006 5:24 PM:
cinthia on 27 Oct 2011 8:20 AM:
does anyone know who wrote this article in the wall street journal and on what page it was mentioned?
referenced by