Re: MSKLC restrictions (was: Ways to show Unicode contents on Windows?)

2013-07-31 Thread Philippe Verdy
Oh well I thought it was a limitation of MSKLC, now your link shows that this is a limitaiton of the keyboard drivers DDK for Windows itself. Deadkeys should be perceived not really as keys but as functions allowing to select temporarily another keymap. These keymaps should just be indexed (16-bit

Re: MSKLC restrictions (was: Ways to show Unicode contents on Windows?)

2013-07-31 Thread Richard Wordingham
On Wed, 31 Jul 2013 22:49:07 +0200 Philippe Verdy wrote: > However, the MSKLC does not allow the target of a (dead-key + another > key) to produce another dead key, it can only produce an ouput string > (containing at most four 16-bit code units). So dead keys cannot be > chained. Michael Kaplan

Re: MSKLC restrictions (was: Ways to show Unicode contents on Windows?)

2013-07-31 Thread Philippe Verdy
NFC versus NFD is not the problem here. One will still want to produce the correct sequence which will be canonically equivalent (possibly not even in any normalized form but still canonically equivalent). You may still want to be able to use dead keys, instead of typing separate keys for each comb

Re: MSKLC restrictions (was: Ways to show Unicode contents on Windows?)

2013-07-31 Thread Richard Wordingham
On Wed, 31 Jul 2013 15:30:02 +0200 Otto Stolz wrote: > Another limitation: Apparently you cannot define sequences > of dead keys. If I am mistaken, I’d appreciate any hint > on how to define dead key sequences, in the MSKLC framework. See http://blogs.msdn.com/b/michkap/archive/2011/04/16/101547

MSKLC restrictions (was: Ways to show Unicode contents on Windows?)

2013-07-31 Thread Otto Stolz
Hello, am 2013-07-30 um 02:11 Uhr hat Ilya Zakharevich geschrieben: [I’m switching to “pedantic” mode since there are so many posts on this list which FALSELY accuse Windows' keyboard system of shortcomings. There ARE many shortcomings, but they are usually buried under an avalan

Re: _Unicode_code_page_and_?.net

2013-07-31 Thread Philippe Verdy
My opinion is that the term "code page" in Windows does not really designate an encoding, or any code page switching at all (dynamic switches with contextual states for the current page). It just indicates an encoding scheme that will be processed by the device specifying it. Winfows complicates t

Re: _Unicode_code_page_and_?.net

2013-07-31 Thread Richard Wordingham
On Tue, 30 Jul 2013 22:02:10 -0700 Stephan Stiller wrote: > On 7/30/2013 3:27 PM, Asmus Freytag wrote: > > architectures that depended on swapping character sets (code > > pages) in mid stream > > I thought systems were usually married to a particular code page. I'm > wondering where (historic