Sorting it all Out Michael Kaplan's random stuff of dubious value Be sure to read the disclaimer here first!
Today's riff will be on the page titled Locale IDs Assigned by Microsoft.
This page, largely produced some time after XP and Server 2003 shipped, by an unknown person or people, has everything.
Like one Sorbian, rather than the two we have in Windows now, using the LCID we call Upper Sorbian:
or a bunch of other locales we've changed the name of for various reasons:
or one I doubt we'll ever have (even if a professor convinced someone to add an LCID years ago!):
There is even one with the wrong LCID!
And a lot more French locales than we've ever shipped:
And a bunch of locales that are likely worth considering some day:
And there are ones we might even be able to add now:
And ones we still can't add yet:
There's even one with [to some] somewhat offensive parathetical text that actually have nine locales now:
You get the point.
This list is insane! It's really the best example of why we should never have lists! :-)
I don't understand the last sentence. The list has a disclaimer that these might not all be implemented.
Isn't "FYRO Macedonian" kind of silly? Greece can complain about the name of the country all they like, and force us all to use the ungainly "FYRO" name, but why apply it to the language?
Yes, but is the list really needed? What purpose does it serve to publish at all any list outside of the one in the protocol docs?
Better yet, simply don't document anything at all. Leave all to be done by people sniffing around the code -- Oh, no code? Well then.
Obviously with gigabytes of docs on MSDN, TechNet, et. al., we don't go that route. But the protocol doc list is responsible and accurate, whereas random lists are just unbound by common sense rules of correctneess.
Always document, but always make sure they are accurate and stay that way....
>or one I doubt we'll ever have (even if a professor convinced someone to add an LCID years ago!):
far vus nisht?