by Michael S. Kaplan, published on 2010/06/01 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2010/06/01/10017368.aspx
It put me in mind of The elusive G-sign said to exist in South America may not be in Windows, says a customer who has hunted for it, it did.
You know, with the Paraguay Guaraní currency symbol (₲, aka U+20b2, aka GUARANI SIGN).
And how Microsoft had added the character to many fonts but had not added it to the locale data.
It would be easy to claim that I'm no longer on the team that is the custodian of the locale data (since I'm not).
It would be easy to claim I hadn't heard about the move to get the currency sign into fonts (since I hadn't).
It would be easy to claim that even when I was on that team I didn't do much of the work in the "data maintenance" space (since I didn't).
And it would be easy to claim that I could not even really recall hearing about this currency sign when it was added to Unicode 4.1 (since I couldn't).
Even so, if one is a part of a company it is easy to feel bad about it. I mean given that it is quite possible if I had involved myself in the right conversation or the right meeting or the right email thread, I could have maybe helped fix this one. I mean, it would have been an alteration to some established procedures, but if I'm gonna be out there anyway I may as well spend a little time above the line trying to change a process/procedure or two when it make sense.
It has happened before, after all.
Perhaps sometimes this Blog is a way of offering up such "flaws" as an attempt to be transparent about them, hoping to be forgiven for the "sin" of not being able to solve every international problem, get every international bug fixed.
Weird the way my mind works, huh? Trust me, I'm a mystery. I really am.
Anyway, today's blog is not about the GUARANI SIGN or about the tinge of regret I feel about missing the chance to fix it before either Vista or Windows 7 shipped, despite the fact that all of the text up until now essentially has been.
Today's blog is about something different.
Remember early last month, when I wrote my blog Kazakhstan (a country 4 times the size of Texas) has its own Windows 7 LIP!?
Well, not too long before that particular Language Interface Pack was released, stakeholders pointed out something amiss.
Looking at the Kazakh locale data:
It has Т (aka U+0422, CYRILLIC CAPITAL LETTER TE) as its currency symbol.
however, you see, the Kazakhstani tenge (теңге), which was introduced in November of 1993, wasn't using the Т anymore.
In March of 2007 they came up with a new symbol to act as the currency sign, and in March 2008 it was proposed as a new character in Unicode. And in Unicode 5.2, it became ₸ (U+20b8, TENGE SIGN), with a note in the Currency block in Unicode of its relation to other similar Unicode characters like ⍑ (aka U+2351, APL FUNCTIONAL SYMBOL UP TACK OVERBAR), ╤ (aka U+2564, BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE), and 〒 (aka U+3012, POSTAL MARK).
It looks like this (thanks Wikimedia for the SVG, click on it to get to them!):
This currency sign, added to Unicode in (as I said) version 5.2, was added too late for it to get into Windows 7 and Windows Server 2008 R2.
It was therefore (unlike with ₲) not present in any of the fonts on the system.
Changing the locale to point to the new character would have consigned the TENGE SIGN to look like an empty square box rather than a currency sign people could use. And a last minute change to multiple fonts would have also been a huge undertaking and would have delayed the LIP's release by an unknown amount of time while solutions were put together for the font and the locale.
Even then it would be missing on the keyboard, in the Unicode property data, in the collation data. Being an "unknown" character like that leads to huge number of strange compatibility problems, believe me. Even when its not a currency sign.
And it likely wouldn't have been in Office either -- neither 2007 (too early!) or even 2010 (which had largely snapped on the Windows 7 data and would have just as many problems with an unknown character as a currency sign).
So in the end, the LIP had to be released without the change, even though one day all of the software pieces and fonts can be in a better position to do the right thing than this currency sign that had the misfortune to be created and encoded in exactly the wrong timeframe to be included in the current generation of products.
Thus it is with a tenge of sorrow that I explain how the tenge is not in Windows 7, or's its Kazakh LIP.
Because even the fact that there was no possible way that it could have happened makes me feel no less gulty about the whole thing.
As amazing DJ Samantha Ronson might say, I wonder if I'm just built this way....
Charles on 3 Jun 2010 11:42 AM:
Thanks for all the work you have been doing, Michael, even the non-Unicode stuff, whatever that may be.
James on 23 Jun 2010 11:14 PM:
Hello Michael. On a related note. The philippine peso sign has been available as unicode 20b1 for ages now (unicode 3). yet the localization keeps using the international symbol Php.
(Other localization related requests.
- Our own time zone (gmt +8 Manila) we keep having to use Taipei. (i hate that)
- legal size paper, ours is 8.5 inches by 13 inches vs. 14 inches in the U.S.
- Our own keyboard. we just need two, the peso sign cited above and the enye (ñ)
which is used in many Spanish proper names. (places, surnames). Maybe use the altGr N combination.
thanks for listening
go to newer or older post, or back to index or month or day