How does Microsoft 'manage' to not correct a spelling error, exactly?

by Michael S. Kaplan, published on 2008/01/07 10:16 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2008/01/07/7000297.aspx


From the recently pre-recorded blogs collection...

Flashback. Well, rewind and flashback. Not too far...

Way back in May of 2005, Denis Onischenko mentioned:

NativeName property of "uk" and "uk-UA" CultureInfo is misspelled.

A few clarifying questions later and the problem was clear: both the .NET CultureInfo.NativeName property and the return of Win32 NLS API call GetLocaleInfo with LOCALE_NATIVELANGNAME return

україньска

instead of

українська

I got the word off to the data owner at the time and she got the fix in. Now Vista spells the language name Ukranian spelled in Ukrainian right.

Downlevel on Windows, the bug is not fixed. Because while a misspelling is embarrassing, it has also existed in Windows since Ukrainian was added in NT 4.0 and it is a really a challenge to call it a security bug that needs to be fixed. The string is not available in the UI (except maybe in installation and/or UI language list after installation of the XP Ukrainian LIP (first mentioned here back in Microsoft, you giving us some LIP?). To date, no one has ever (as far as I know) reported the problem on any Windows platform....

Of course, it has now been nearly 2.5 years and several versions of the .NET Framework have shipped, yet the bug is still not fixed in the managed case and the CultureInfo.NativeName property, though that has to do with the fact that little to no updates have been made to the built-in data in the .NET Framework in any of those releases (if memory serves a bunch of bug fixes from the XP SP2 locale work were picked up, but I think there were some bugs in those updates not found until it was too late to fix them, which soured people on the update story a tad?).

The impact is that this misspelling is still sitting there in .NET even in the Orcas release, which is enduring proof that Microsoft can't always manage to spell thing correctly....

Now how important is this kind of bug? Hard to say. I mean, how many people would think if weird if I talked about Sotring it all Out, Mihcael Kalpan's radnom stuff of duboius value, other than me? some bugs are just really embarrassing....

In the end, I honestly have no real clue when a fix or update is planned here.

To get a report on this letter we will head over to Ukrainian Power and ask Boomchyk how a real Ukrainian person would pronounce what under-Ukrainian-educated unicode folks like myself call the CYRILLIC SMALL LETTER SOFT SIGN. Thanks, Boomchyk!

Hmmm.... I wish I could have gotten out of doing fifth grade spelling tests for Ms. Simon with a note from Microsoft about it!

 

This post brought to you by ь (U+044c, aka CYRILLIC SMALL LETTER SOFT SIGN)


# Igor Tandetnik on 7 Jan 2008 12:24 PM:

The soft sign is silent. What it does is alter the pronunciation of the preceding consonant. For example, 'н' (cyrillic letter en) usually sounds like 'n' in 'no'. 'нь' (en followed by soft sign) sounds like 'n' in 'new'.

Boomchyk doesn't really pronounce the soft sign (it doesn't have a pronunciation of its own), but spells out the letter's name. That is, he literally says "soft sign".

# Michael S. Kaplan on 7 Jan 2008 12:44 PM:

Like how I look at "W" and say "double you" in English -- the letter name is not the letter sound (and for this letter that is the only choice since it has no independent sound of it own...).

Cool!

# John Cowan on 7 Jan 2008 2:27 PM:

Note that most anglophones in the Western Hemisphere pronounce "no" and "new" the same way, with the hard (non-palatalized) "n".  Spanish n-tilde or French/italian gn is more like it.


go to newer or older post, or back to index or month or day