Win 7 RTM & Arabic: "We can fix up August and April. But it'll cost you July to do it…"

by Michael S. Kaplan, published on 2011/02/09 08:19 -08:00, original URI: http://blogs.msdn.com/b/michkap/archive/2011/02/09/10125506.aspx


Alternate titles taking U+0648 (Waw) U+062a (Teh) U+0641 (Feh) into some kind of WTF homage pun that might even be vaguely relevant were discarded as being too obscure for some readers and too stupid for the ones who would get it....

There are few times when one says things like "two steps forward, one step back" is it so literally the case.

But this might very well be one of those times.

It starts with the localized names of the Gregorian months in nine of the Arabic locales on Windows.

So here is what they look like:

in English in Arabic
January يناير
February فبراير
March مارس
April ابريل
May مايو
June يونيو
July يوليو
August اغسطس
September سبتمبر
October اكتوبر
November نوفمبر
December ديسمبر

Now these month names (which were in nine different Arabic locales in Windows) weren't exactly wrong. Neither were the day names. Most of them were fine, as they were.

But over in Office some of them were slightly different.

Like that fourth month, the one people call April?

Well Windows had it as ابريل but Office had it as أبريل.

It's a subtle difference, but Windows was starting with an ARABIC LETTER ALEF while Office was using an ARABIC LETTER ALEF WITH HAMZA ABOVE. Neither was wrong per se, but everyone felt that even though they are both "right" that the Office way was a little more right.

You can look up more about the Hamza on Wikipedia here:

Hamza is not one of the 28 "full" letters, and owes its existence to historical orthographical inconsistencies in early Islamic times. In the Phoenician and Aramaic alphabets, from which the Arabic alphabet is descended, the glottal stop was expressed by ʼāleph, continued by Arabic alphabet ʼalif. However, alif was used to express both a glottal stop, and a long vowel /aː/. To indicate that a glottal stop, and not a mere vowel, was intended, hamza was added diacritically to alif.

This might help make it clear why one might generally be considered more right....

Life in Windows without the Hamza hadn't really been so terrible, mind you. And I wouldn't want to apply that it had been.

But there was this inconsistency, and of course anyone using managed code in Office might have run into that inconsistency in weird ways what with random parsing and formatting -- like if they were using managed code and interacting with results from Office itself.

Not that I don't think some of those scenarios aren't also totally broken too. But we'll get into that some other day!

Anyway, Windows decided to fix up these cases, so that in Windows 7 they would have all of the names the way that was more right -- the Office way, in this particular case.

So the updates happened.

And now, August and April would be safe for Windows 7 in nine Arabic locales (ar-BH, ar-EG, ar-KW, ar-LY, ar-OM, ar-QA, ar-SA, ar-AE, and ar-YE, to be specific). This happened in time for Windows 7's release.

But there was one problem here.

Yep, they replaced يوليو, by which I mean July (a month that was not broken) with يوليه.

In the process of adding Hamzas to two Alefs, an ARABIC LETTER WAW was replaced with an ARABIC LETTER HEH.

That "Wah Teh Feh" pun is almost taking shape for you now, right? :-)

This is obviously a problem. This is in fact the problem I was indirectly talking about last year in I'm going to throw a hypothetical on the stoop and see if the cat licks it up.

For people who didn't get the update (you may recall the challenges in detecting who might that I brought up in that blog) but really want it and don't mind the reboot, you can wait for SP1 (which rolls up this sand other changes), or you get it from the following KB article:

Arabic translations in the month of July may be incorrect in the Windows calendar in Windows 7 or in Windows Server 2008 R2

and this will fix up the problem.

The fancy language in the KB article and the download pages is to try to work around the fact that the fix was pushed to some people already. So don't feel like you need to gratuitously pick up this fix if you aren't interested, or might already have it....

Anyway, at the start I pointed out how the whole "two steps forward, one step back" seemed awfully literal here, what with Windows 7 fixing April and August while breaking July. Technically there are is also the abbreviated July, the abbreviated April and August, two day names with the original Hamza issue, and the abbreviated forms of those two days two. It's just that "8 steps forward, 2 steps back" seems so much less catchy!


comments not archived

referenced by

2011/03/22 Rupee! Rupee! Let down your CHAR!

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