Monday, June 25, 2007 8:47 AM
Michael S. Kaplan
Sometimes when you say 'the fix is in' you mean it in a good way
It was just a few months ago that that I posted about a particularly bad bug in Vista in Double Secret ANSI, part 2 (the brokenest one yet, sorry 'bout that!).
And of course our favorite Romanian Cristian Secară has talking about this bug in the newsgroups recently, going so far as to suggest that people may want avoid upgrading:
This is not always a pure appication issue. For example most television subtitling formats are 8 bit. This is likely to be changed only in the broadcast industry if/when/with the introduction of the new XML-based EBU subtitling format, but even this is doubtful to be properly implemented because somewhere in the specifications they require backward conversion possibility to the old format (which actually is a misery, being based on ISO/IEC 6937).
Because practically all subtitling formats are 8 bit (.sub, .ssa, .srt, etc.), applications don't feel the need to switch to Unicode just for themselves. Western countries don't use subtitling, so there is no push from the software industry here in the Unicode direction.
So we must preserve some 2000/XP systems in the long term just to have proper subtitling on the screens. It is good to know ...
Thankfully, things are not quite this dire. :-)
And please note that it has nothing to do with bug, whatsoever, since it only impacts keyboard input in these applications!
The fix for the actual problem is going into Vista client SP1 (and is in Server 2008 as well). And for those who really don't want to wait (I do not know the exact dates myself), it is available as as hotfix now.
The article will be KB 936060 (the article is not yet public) , but if you are running to this problem of some keyboard languages not working correctly in non-Unicode applications, you can talk to someone in Microsoft product support and get this hotfix (they can find it via the KB article in their tools) and since it is a bug you shouldn't be charged for the contact....
Cristi raises and excellent point about the non-Unicodeness of specific components of applications that may themselves be in Unicode. I will need to talk about that issue a bit at some point. :-)
But for now, if you need a fix to this problem, there is a way to get it. And soon everyone running Vista will be getting it.
The fix is in, truly....
This post brought to you by ț (U+021b, a.k.a. LATIN SMALL LETTER T WITH COMMA BELOW)