Windows keyboard restrictions

Eli Zaretskii eliz at
Sat Aug 8 09:31:30 CDT 2015

> Date: Sat, 8 Aug 2015 16:22:57 +0200 (CEST)
> From: Marcel Schneider <charupdate at>
> I'm very puzzled about this being UTF-16 code units, as stated also in the
> MSKLC Help. In the driver source kbd*****.c, each of those entities is referred
> to as WCHAR, which is meant to mean (^^) "UNICODE CHARACTER". Indeed we can
> write 0x1234 for a given WCHAR in a driver source, but also 0x101234 for
> another given WCHAR if that's its code point. Nowhere there is any UTF
> appearing. Despite of having looked up the Unicode FAQs about Unicode
> transformation formats, I'm unable to make the link.

The Windows WCHAR is a 16-bit data type.  What Windows documentation
calls "Unicode characters" are Unicode codepoints encoded in UTF-16.

More information about the Unicode mailing list