From: Michael \(michka\) Kaplan (michka@trigeminal.com)
Date: Mon Apr 26 2004 - 15:34:58 EDT
From: "Philippe Verdy" <verdy_p@wanadoo.fr>
> From: "Shawn Steele" <shawnste@winse.microsoft.com>
> > >> A keyboard can generate a single or combined character in few
different
> >
> > For the keyboard you can use MSKLC
> http://www.microsoft.com/globaldev/tools/msklc.mspx even with the
necessary
> multiple code point characters that you need.
>
> Yes it works for the final generated sequences, but MSKLC won't work with
> multiple dead keys, as MSKLC only supports combinations like:
> <dead key> + <base code point> ==> <unicode string>
>
> So to allow entering I + curcumblex + acute, one would need to map:
> <acute dead key> + <I-circumflex code point>
> but there's no way to compose I-circumflex if it does not receives a
single
> keystroke assignment (without dead keys).
>
> There's no support in MSKLC to create mapping with 2 dead keys + one base
code
> point.
Actually, there is no support in the Windows DDK header file that controls
keyboard layouts (kbd.h) for this. Only one UTF-16 code point can be the end
result.
MSKLC is very far downstream of the architecture here.
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
This archive was generated by hypermail 2.1.5 : Mon Apr 26 2004 - 16:16:29 EDT