On 20 Aug 2015 at 03:19, Richard Wordingham wrote:
On Mon, 17 Aug 2015 13:51:26 +0200 (CEST)
Marcel Schneider wrote:
Since yesterday I know a very simple way to get the source code (in
C) of any MSKLC layout.
Is this legal? To me it smacks of reverse engineering, which is
prohibited
On 18 Aug 2015 at 10:09, Philippe Verdy wrote:
i don't know why these c source files need to be deleted so fast when they
could just remain in the same folder as the saved.klc file.
Iʼve missed the point when I replied on 18 Aug 2015. In fact, thereʼs no short
answer (which BTW would be
On Mon, 17 Aug 2015 13:51:26 +0200 (CEST)
Marcel Schneider charupd...@orange.fr wrote:
Since yesterday I know a very simple way to get the source code (in
C) of any MSKLC layout.
Is this legal? To me it smacks of reverse engineering, which is
prohibited under the MSKLC licence.
Richard.
On 18 Aug 2015 at 10:09, Philippe Verdy wrote:
it helps if hou reduce the processor frequency (if you don't have a tool fir
that, use the energy control panel and set the power profile to max energy
saving) just before clicking the button to build the package.
That's a very good idea. I've
it helps if hou reduce the processor frequency (if you don't have a tool
fir that, use the energy control panel and set the power profile to max
energy saving) just before clicking the button to build the package.
i don't know why these c source files need to be deleted so fast when they
could
On 07 Aug 2015, at 20:54, Richard Wordingham wrote:
What we're waiting for is a guide we can follow, or some code we can ape.
Since yesterday I know a very simple way to get the source code (in C) of any
MSKLC layout.
While the build is done, we must wait for the four files appearing in an
On 8/11/2015 11:51 AM, Marcel Schneider
wrote:
All that, and some more, leads me to the
conclusion that when Windows was built, there was often not
enough time to write up the documentation;
Marcel,
please consider that this musing
Iʼve got a driver with a five code units ligature on Shift+Ctrl+Alt, and where
Word (and Excel) opened. As I was in a hurry and wrote in English, I didnʼt
notice that the dead keys were disabled. That was the driver I was writing
about when I spun off this thread.
Now Iʼve compiled a driver
On 10 Aug 2015, at 13;21, I wrote:
I note that the MSKLC converts to ligatures of a surrogates pair any SMP
character mapped on a key, and that it cannot admit any SMP character in a
dead list.
Such an MSKLC layout with U+1D4EA 퓪 and U+1D4D0 퓐 works on the built-in
Notepad, while Word
I'm brought to draw your attention to the fact that presumably my buggy
mailbox inverted the order of the Copy Addressees, which I find reversed in
both mailboxes where I can follow (but not answer in both, under my name
associated with a fitting custom mail address).
This order is mainly
Hi Max,
On 10 Aug 2015, at 20:25, Max Truxa wrote:
IMO this mailing list is not the right place for questions about C syntax, is
it not?
Indeed it isn't. Would it not be about Unicode implementation, I wouldn't have
sent it to the Unicode Mailing List.
Whatever language, it's about
On Mon, 10 Aug 2015 21:46:39 +0200 (CEST)
Marcel Schneider charupd...@orange.fr wrote:
Correct syntax would be: [...] 0xD835, 0xDCEA, 0xD835, 0xDCD0, [...]
The problem with the commas here is that they don't only separate,
they increment the modification number. The trailing surrogate must
I confused the parent thread labelling. Please read:
The role of documentation in implementation (was: Re: Windows keyboard
restrictions)
On 08 Aug 2015, at 15:01, Richard Wordingham wrote:
On Sat, 8 Aug 2015 14:05:17 +0200 (CEST)
Marcel Schneider wrote:
2. Supposed that Windows
On Saturday, 8 August 2015, Richard Wordingham
richard.wording...@ntlworld.com wrote:
Michael did do a series of blog posts on building TSF based input methods
years ago. Something I tinkered with off and on.
What we're waiting for is a guide we can follow, or some code we can
ape. Such
On Sat, 8 Aug 2015 17:05:26 +1000
Andrew Cunningham lang.supp...@gmail.com wrote:
On Saturday, 8 August 2015, Richard Wordingham
richard.wording...@ntlworld.com wrote:
Michael did do a series of blog posts on building TSF based input
methods years ago. Something I tinkered with off and on.
On 08 Aug 2015, at 00:18, Doug Ewell wrote:
Marcel Schneider wrote:
I just donʼt want to let the Mailing List believe that I agreed being
classified as «fighting the [bad] fight»
And I don't think Michael implied that. I just want to get the technical
facts, so that hopefully they can
I think about another bug in my mailbox, so that this mail I sent in Plain
Text on Thu, 6 Aug 2015, landed all wrecked in the Archive.
Please may I resend this for that behalf.
(I already ended up replacing all and by single angle quotation marks.)
If you are a Mailing List subscriber,
On 08 Aug 2015, at 02:19, Andrew Glass (WINDOWS) wrote:
Sorry to be late to this thread. I'm the Program Manager responsible for
MSKLC at this time. As far as the history here, I can only reiterate
Michael's point that making significant changes to user32.dll faces
significant, perhaps
On Sat, 8 Aug 2015 14:05:17 +0200 (CEST)
Marcel Schneider charupd...@orange.fr wrote:
2. Supposed that Windows supported more than four characters per
ligature:
2.1. Why has the MSKLC been limited to four characters per
ligature?
Because that was believed to be the architectural limit.
On 08 Aug 2015, at 00:30, Doug Ewell wrote:
Marcel Schneider wrote:
I brought the good news that SIXTEEN UNICODE CODE POINTS can be
generated by a single key stroke on Windows six dot one. The only bad
news, because of which I've e-mailed to the List, is that that wasn't
working in
On 08 Aug 2015, at 15:01, Richard Wordingham wrote:
On Sat, 8 Aug 2015 14:05:17 +0200 (CEST)
Marcel Schneider wrote:
2. Supposed that Windows supported more than four characters per
ligature:
2.1. Why has the MSKLC been limited to four characters per
ligature?
Because that was
Date: Sat, 8 Aug 2015 16:22:57 +0200 (CEST)
From: Marcel Schneider charupd...@orange.fr
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 (^^)
On 08 Aug 2015, at 16;39, Eli Zaretskii wrote:
The Windows WCHAR is a 16-bit data type. What Windows documentation
calls Unicode characters are Unicode codepoints encoded in UTF-16.
Thanks a lot!
Best regards,
Marcel Schneider
On Sat, 8 Aug 2015 16:22:57 +0200 (CEST)
Marcel Schneider charupd...@orange.fr wrote:
Further, we're awaiting the responses from Mr Glass at Microsoft.
See http://unicode.org/pipermail/unicode/2015-August/002465.html .
More information would take time.
Richard.
, CO
From: Marcel Schneider
Sent: Saturday, August 8, 2015 6:05
To: Andrew Glass (WINDOWS)
Cc: Doug Ewell ; Unicode Mailing List
Subject: RE: Windows keyboard restrictions
On 08 Aug 2015, at 02:19, Andrew Glass (WINDOWS)
andrew.gl...@microsoft.com wrote:
Sorry to be late to this thread. I'm
On 8/8/2015 6:26 AM, Marcel Schneider
wrote:
a useless worsening of the usability and of the usefulness of a product.
Quote of the day.
A./
Richard Wordingham richard.wording...@ntlworld.com wrote:
On Sat, 8 Aug 2015 17:05:26 +1000
Andrew Cunningham lang.supp...@gmail.com wrote:
Michael did do a series of blog posts on building TSF based input
methods years ago. Something I tinkered with off and on.
Does this mean that one
On 08 Aug 2015, at 19;45, Doug Ewell wrote:
Now that I know Andrew is the PM for MSKLC ¹,
Probably Mr Glass wasn't Mr Kaplan's boss, so he is to overtake a legacy
without having been involved in its generating. I didn't well notice the
chronological relationship, so I asked questions whose
On 8/8/2015 1:57 PM, Marcel Schneider
wrote:
Now that I know Andrew is the PM for
MSKLC ¹,
Probably Mr Glass wasn't Mr Kaplan's boss, so he is to
overtake a legacy without having been involved in its
generating. I didn't well notice
Richard Wordingham richard dot wordingham at ntlworld dot com wrote:
It's good to see he's still with us.
Still out there, just not on this list.
What we're waiting for is a guide we can follow, or some code we can
ape. Such should be, or should have been, available in a Tavultesoft
Keyman
Marcel Schneider charupdate at orange dot fr wrote:
I just donʼt want to let the Mailing List believe that I agreed being
classified as «fighting the [bad] fight»
And I don't think Michael implied that. I just want to get the technical
facts, so that hopefully they can take the place of
Marcel Schneider charupdate at orange dot fr wrote:
I brought the good news that SIXTEEN UNICODE CODE POINTS can be
generated by a single key stroke on Windows six dot one. The only bad
news, because of which I've e-mailed to the List, is that that wasn't
working in one single circumstance.
Michael Kaplan, author of MSKLC, reports that not only is the limit on
UTF-16 code points in a Windows keyboard ligature still 4, it is likely
to remain 4 for the foreseeable future:
http://www.siao2.com/2015/08/07/8770668856267196989.aspx
People who want input methods capable of handling more
On Fri, 07 Aug 2015 09:26:56 -0700
Doug Ewell d...@ewellic.org wrote:
Michael Kaplan, author of MSKLC, reports that not only is the limit on
UTF-16 code points in a Windows keyboard ligature still 4, it is
likely to remain 4 for the foreseeable future:
On 07 Aug 2015, at 18:38, Doug Ewell wrote:
Michael Kaplan, author of MSKLC, reports that not only is the limit on
UTF-16 code points in a Windows keyboard ligature still 4, it is likely
to remain 4 for the foreseeable future:
http://www.siao2.com/2015/08/07/8770668856267196989.aspx
On 07 Aug 2015, at 21:04, Richard Wordingham wrote:
On Fri, 07 Aug 2015 09:26:56 -0700
Doug Ewell wrote:
Michael Kaplan, author of MSKLC, reports that not only is the limit on
UTF-16 code points in a Windows keyboard ligature still 4, it is
likely to remain 4 for the foreseeable
To: Unicode Mailing List unicode@unicode.org
Cc: Marcel Schneider charupd...@orange.fr
Subject: Re: Windows keyboard restrictions
Marcel Schneider charupdate at orange dot fr wrote:
I brought the good news that SIXTEEN UNICODE CODE POINTS can be
generated by a single key stroke on Windows six dot
On Thu, 06 Aug 2015 10:56:51 -0700
Doug Ewell d...@ewellic.org wrote:
Richard Wordingham richard dot wordingham at ntlworld dot com wrote:
The UK has been discussing whether a certain user-perceived
character should be encoded as a single character in a new script.
Users ought to have
Richard Wordingham richard dot wordingham at ntlworld dot com wrote:
It's part of an unencoded, living script. There is no suitable
contiguous place for the script in the BMP. There is a set of
characters within the script that appear to be sequences of three
characters, and encoding these
Richard Wordingham richard dot wordingham at ntlworld dot com wrote:
The UK has been discussing whether a certain user-perceived character
should be encoded as a single character in a new script. Users ought
to have this character on their keyboards, but there is a worry about
technical
On Thu, 06 Aug 2015 09:00:21 -0700
Doug Ewell d...@ewellic.org wrote:
Seriously, please take this to Microsoft or to one of the forums where
the Driver Development Kit is discussed. This has nothing to do with
Unicode.
That depends on the availability of Tavultesoft Keyman. The UK has been
On 2015-08-06, Richard Wordingham richard.wording...@ntlworld.com wrote:
That depends on the availability of Tavultesoft Keyman. The UK has been
discussing whether a certain user-perceived character should be encoded
as a single character in a new script. Users ought to have this
character
I've got a bug in my mailbox. While taking care to send my e-mail in plain
text, I got it converted somehow to HTML with all tags disappearing.
So I ended up replacing all and by single angle quotation marks. That seems
safer than converting them to HTML codes.
Perhaps I shouldn't call it a
A part of the documentation you request is available:
“Download Windows Driver Kit Version 7.1.0 from Official Microsoft Download
Center.” N. p., 1 Dec. 2014. Web. 1 Dec. 2014.
https://www.microsoft.com/en-us/download/details.aspx?id=11800
C:\WinDDK\7600.16385.1\inc\api\kbd.h
Line 469, and
Marcel Schneider charupdate at orange dot fr wrote:
A part of the documentation you request is available:
“Download Windows Driver Kit Version 7.1.0 from Official Microsoft
Download Center.” N. p., 1 Dec. 2014. Web. 1 Dec. 2014.
https://www.microsoft.com/en-us/download/details.aspx?id=11800
Marcel Schneider charupdate at orange dot fr wrote:
The bug on Windows I encountered at the end of July has been
definitely identified and reconstructed. After ninety-five drivers
compiled since the bug appeared, I can tell so much as that the
problem is related to the length of the so-called
46 matches
Mail list logo
