by Michael S. Kaplan, published on 2007/02/04 19:07 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2007/02/04/1600427.aspx
The keyboard layout for Inuktitut has a fascinating history on Windows, even though it really only dates back to the post-XP SP2 ELK package in KB897338 that I mentioned here.
That first version only provides support for the Latin script. There was a real push to support more, but given that the Canadian Syllabics subrange in Unicode had no weight in the collation tables, the results of trying to use it would have been less than optimal. So the keyboard was floated with various informants and held until Vista, and the Latin script support is all that shipped.
(As a miscellaneous note of interest, there was a push to provide a special sort for the Latin script version of Inuktitut, but as it turns out the results it provided for anything in either English or French was bad enough that it just didn't make very much sense to pick up as a collation for the locale, yet another example of the phenomenon I mentioned first when talking about a Cantonese sort -- an attempt to provide a functionality fails due to the disappointing results trying out the prototype!)
Anyway, the Latin script keyboard is nothing special (as compared with many other Windows layouts, at least!).
But then move into Vista and with the Gavin Nesbitt-provided layout things start to get more interesting. Here it is in the BASE, SHIFT, ALTGR, and ALTGR+SHIFT states:
As you might guess, the BASE and SHIFT states are almost identical to the older Latin script keyboard. Which is I suppose good for compatibility (though I have my doubts about how many people installed that particular QFE who were concerned about Vista compat for their keyboard layout experience!). But there is another problem here....
If you were typing with the Syllabics, you might be really unhappy if every letter you typed required hitting the Right ALT (AltGr) key. So the SGCAPS and SHIFT+SGCAPS state was also used:
And there is also that one last difference back in the BASE state -- that dead key, which looks like this:
Oops, let's not do this on XP, let's do it on Vista where the font is installed and Uniscribe knows what to do with it:
Display automatically working in ToolTips even though it is unlikely that the font will have the characters is the kind of feature uses that new special not-yet-defined definition of complex scripts that I talked about in this post....
So basically you have three different ways to type in characters -- the dead keys, the SGCAPS assignments, or the AltGr assignments. It is probably not as likely that usage of the three would overlap; I suspect a user would pick one to learn and go with it. Just my impression.... though it does make for a very interesting use of SGCAPS that I would tentatively call a good idea and an exception to my usual thoughts on the functionality....
Last note -- the font being used in Vista is Euphemia, and I have no idea what the backstory is for that font name. :-)
This post brought to you by ᙱ (U+1671, a.k.a. CANADIAN SYLLABICS NNGI)
# Gavin Nesbitt on 20 Mar 2007 10:45 PM:
I just noticed your post...For the general interest of those who might search on this, the latin keyboard does contain a few things of interest.
A few characters were never (easily) available for input. They usually had poor substitutes such as the "&" instead of the "ł" (barred l). Very unnattractive
The character references are:
ł (u+0142) used to represent the U+15A0... (ᖠ) type syllabics
ŋ (u+014B) used for the U+1671...(ᙱ) type syllabics you used above.
These particular characters are also in the Vista syllabic keyboard, but they do help a number of users attempting to do Inuktitut latin in XP.
Thanks for your post!
go to newer or older post, or back to index or month or day