When one dishes it out but can’t take it (aka Raising the roof, 2010 edition)
Do you know that old saying Don’t dish it out if you can’t take it , by any chance? Microsoft doesn’t always follow this, from a technical perspective.
You Myanmar’ing me? You Myanmar’ing *me*? You must be Myanmar’ing me, there’s no one else here!
In response to This is not yet my take on DirectWrite , Ravi Chhabra asked (in a comment ): Hi Michael, I note that you interest lies in: “what’s missing — what scripts, what languages, what scenarios” In that light I wanted to know if you could shed some lights on why Myanmar Font is mentioned as system supported in the DirectWrite documentation, while in fact it’s not there in the system? Thanks. and in the Suggestion Box: There is a slide by Anantha Kancherla: http://download.microsoft.com/download/5/E/6/5E66B27B-988B-4F50-AF3A-C2FF1E62180F/GRA-T515_WH08.pptx On slide number 44 it list the scripts supported by DirectWrite, which clearly includes Myanmar.
Yes, Ivo^H^H^HVirginia, there is a zh-HK *and* a zh-TW
Over in the Suggestion Box, Ivo asks: I am working on a software that has to support all languages available for Windows.
Seeing double? You’re not drunk; you’re just running pseudo! (aka Announcement: Pseudo Day!)
Some of you regular readers 1 might recall LOCALE_SDECIMAL?
Silly money equivalency games work both ways (aka Making your localizer’s life easier, Part 3)
As series go, this one is not happening nearly as fast as I might have liked. The first one, How many ways can a developer say ‘File Not Found?’ (aka Making your localizer’s life easier, Part 1) , happened in the end of December, 2007.
From KLID to GUID (aka KLIDoral stimulation, it feels GUID)
Apologies for the title (note to self: never author blog titles under the inflluence to try to appear as a cunning linguist!) So it was just the other day that Yong asked: Ok, so it looks like we got a regression (or a design change) on Vista/Windows 7 from Windows XP. On XP/W2K3: ============Start of regopts.txt============ [RegionalSettings] InputLocale = 0409:00000409,0404:E0020404 ============End of regopts.txt============ // Just having this adds for example the Chinese Traditional (ChangJie) keyboard. On Windows Vista SP2/W2K8 SP2 ============Start of regopts.xml============ <gs:GlobalizationServices xmlns:gs=”urn:longhornGlobalizationUnattend”> <!– User List–> <gs:UserList> <gs:User UserID=”Current” CopySettingsToSystemAcct=”true” /> </gs:UserList> <!–System locale–> <gs:SystemLocale Name=”zh-TW”/> <gs:InputPreferences> <!–en-US–> <gs:InputLanguageID Action=”add” ID=”0409:00000409″ Default=”true”/> <!–zh-TW-ChangJie–> <gs:InputLanguageID Action=”add” ID=”0404:E0020404″/> </gs:InputPreferences> </gs:GlobalizationServices> ============End of regopts.xml============ It fails with: Unexpected Failure. Unsupported parameter
On not looking at Uyghur through a Chinese prism
I just remembered that I have a Suggestion Box! In it, Abdusalem asked: Hi Michael, I would like to ask/or suggest as a topic something about the Uyghur (PRC) locale in Windows 7. This is a new locale that has been supported by Windows since Windows Vista as you might know. The current default code page of this locale is set to Arabic (Windows-1256) but this code page cannot fully support the script of Uyghur since it lacks some essential Uyghur-specific characters (ې ,ۈ ,ۇ ,ۆ ,ە). These characters are five out of eight vowel letters in Uyghur, not providing support for these five letters means it does not make any sense for Windows-1256 to be the default code page. Does it have to be the default for the Uyghur (PRC) locale anyway
I know I’ll Never say Never… again, at least
So, thinking about consequences of the CASING piece of Every character has a story #33: U+1e9e (CAPITAL SHARP S, Microsoft edition – Part 2) .
Atlas? Jove? Where’s my Wubi? (The latter shrugged, the former nodded)
So some people noticed that the Wubi IME that used to work on Windows wasn’t there anymore. You may be familiar with the story — it was there for them in XP but then for Vista (and Windows 7) it wasn’t. The funny thing for me about the Wubi IME is that when I hear the name I have trouble getting the Mr
The whole truth about MB_PRECOMPOSED and MB_COMPOSITE
As a by the way, this blog does NOT represent anything beyond my own personal thoughts. You could even blame it on my Tegretol dosage, to be perfectly honest (if the pain were not so intense I’d have skipped this med for sure). I am not even on the team that owns this code any more and I didn’t own it when I was then
The Whey doesn’t get a locale, either
As a by the way, this blog does NOT represent anything beyond my own personal thoughts based on the way I think things are going. You could even blame it on my Tegretol dosage, to be perfectly honest (if the pain were not so intense I’d have skipped this med for sure).
The road to hell is paved with attempts at being compatible
In one of the very first blogs I wrote, I pointed out that Microsoft does not use the Unicode Collation Algorithm . Believe it or not, at the time some people actually asked me whether I thought I might get in trouble for that blog. Looking at it now I can’t even imagine why they would have thought that — there are so many other blogs that are much more effective at getting me into trouble, after all.
