Sorting it all Out Michael Kaplan's random stuff of dubious value Be sure to read the disclaimer here first!
For a long time, I have been talking about how much LCIDs suck.
Blogs like Your LCID sucks and It is true that your LCID sucks, but your LANGID sucks more, in particular, try to make the point.
The underlying practical issues that are often referenced, such as in blogs like Why do LCIDs skip around so much? and Walking off the end of the eighth bit.
And all of that is true.
But I think Jon Stewart's Rally To Restore Sanity has had a little bit of impact on me.
Alythough it is a really good idea to stop depending on LCID and LANGID numbers, the truth is that some people and more importantly some tools still do depend on them.
They will never be as completely flexible and as able to conform to standards and as extensible as using locale names, but for the languages that Microsoft itself has to support, the tendency to keep allocating LCID values is one that cannot simply stop. Because there are quite simply too internal tools and processes that break if they do not have these numbers to work with.
When I point out problems like Walking off the end of the eighth bit, I am falling in to the trap of those who would support the literal rhetoric of Stephen Colbert's March To Keep Fear Alive.
I am fear-mongering, making you afraid of what might break based on the code people might have created years ago that would break once Microsoft ran out of 8-bit LCID values.
Which kind of ignores the fact that the most worrying of them, conceptually -- 0x0501 -- has already been allocated, for pseudo, and thus no actual locale will be mistaken for Arabic.
And which also ignores the fact that if there are other, similar "dangerous" LCIDs then they can simply be skipped, just like Office skipped the number thirteen in their version releases (makes you wonder what they and other Microsoft products plan to do in 2013, doesn't it?).
And which also ignores the fact that while the LCID model cannot scale to either every language in the Ethnologue nor any arbitrary custom locale that it can certainly scale to the (comparatively modest) number of locales and user interface languages that Microsoft has to support in its products.
Just remember to keep the following in mind:
and I will stop trying to use scare tactics to convince people.
We need to restore sanity, not keep fear alive....
What the heck? Dubious value indeed.
Hmmm.... more specific, please?
Just like the light bulb joke on Microsoft, MSFT will declare 2013 as 2014 and continue :)
I imagine that in 2013 they will do the same thing they did in 1996, 1999, 2001, 2004, 2005, 2006, and 2009.
Since the decisions and marketing strategies and conversations were really not the same for any of those, I think that counts as a genuine non-answer. :-)
My point being that there simply does not happen to be any version of Office or Windows named for any of those years. Since the products don't have an annual release cycle like cars, there isn't any reason to think that there would even ordinarily be one called "Office 2013".
13 is bad luck. Of course, this meant that my code's assumption that 2010 would have internal version number of 2007 (12) + 1 meant my office addin's version detection routine would fail. Oops, always should double check that sort of thing.