by Michael S. Kaplan, published on 2010/05/18 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2010/05/18/9997861.aspx
Please forgive the Marty McFly allusion in the title!
When I wrote Capitalized tag != capitalized month (not for nothing, but it was the least-read blog of mine in recent memory!), I only had half the question there.
It was a side question the support person asked as they were looking at the actual question.
The actual question was about the fact that between XP and Windows 7, there was a change.
You can see it right here:
The month name used to be capitalized.
And now in Windows 7 it isn't, apparently:
This underscores a particular reality about our locale data: the fact that it is constantly changing.
Changing due to new preferences.
Changing due to new standards.
Sometimes even changing due to bugs.
In this case, it looks like a change due to standards, as one of the developers noticed:
Having the month in lower case is the right thing to do for Spanish.
Your customer can refer to the following official document, published by the RAE (Royal Academy of the Spanish Language):
http://www.rae.es/rae/gestores/gespub000015.nsf/(voanexos)/arch7E8694F9D6446133C12571640039A189/$FILE/Ortografia.pdf , especially section 3.4.
Also, the AML (Mexican Academy of Language) has the same document:
This kind of thing happens often, and of course if the information is received in reasonable time to take the update then the next version will see that update happening.
Of course if the source needs to be verified that can take more time but the advantage of it being based on a standard is that the source is usually quite quick/easy to verify.
Microsoft gets a non-trivial amount of direct feedback suggesting direct changes being needed in a market without any validation that turn out to be incorrect for the majority of people using the locale. Not for mean-spirited reasons, just for the simple fact that not everyone knows what the "official" way is just because it is the way that seems most natural to them.
But that occasionally leads to bugs, like in this case, for example - a bit of well-intended feedback from one group of native speakers of a language leading to a major bug in the opinion of another group of native speakers....
The big question that comes up is what to do about the down-level versions of Windows, all of which contain the "best known data" from when they were shipped but after that could be "wrong" for any of the three reasons given above or any combination thereof.
The policy, almost without exception, is to change nothing.
Upgrade is the way to get the latest.
In fact, the only time you see exceptions would be very extreme cases, such as new countries moving to use the Euro, and even in that case they are "fixed" by using the built-in "current locale modification" rather than by updating the underlying binary.
Of course within a country it is unlikely to every single person following such standards so readily that a change leads to instant 100% adoption, so there are always going to be people who will consider such changes to be bugs, by default.
Given the potential impact on parsing and formatting, it is quite possible it can look that way in some cases.
All of which is a good reason to not be so completely proactive that the second a standard comes out Windows gets it -- since it can be years or even never before a standard is widely adopted in some cases....
go to newer or older post, or back to index or month or day