public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Ronald Landheer" <info@rlsystems.net>
To: "Marius Gedminas" <marius.gedminas@uosis.mif.vu.lt>, <cygwin@cygwin.com>
Subject: RE: German Win98, US Win95 keyboard --> no ;'` keys in Bash
Date: Fri, 21 Sep 2001 06:02:00 -0000	[thread overview]
Message-ID: <NFBBLOMHALONCDMPGBLFAEPBCBAA.info@rlsystems.net> (raw)
In-Reply-To: <20010921005843.C9385@gintaras>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]

Hello Marius,

> I think the only constructive thing I can suggest at the moment, is to
> compile and run the attached program -- it displays raw console
> keyboard events Cygwin (and any other Win32 application) gets from the
> operating system.
I've compiled and run the program on the clean azerty system I have here 
(from a floppy w/ the cygwin dll on it). It works like a charm, 
including the AltGr button. The only thing is doesn't get is the ê and ë 
like things that French keyboard can automagically handle, but I'm 
assuming that's a codepage problem (though I'm not 100% sure).

The output of trying to type ë (without using the ASCII code as I'm used 
to on my QWERTY machine) is like this:
-- BEGIN SCREEN SNIPPET --
KeyDown (*1) 0010 002A ' ' U+0000 00000030  <-- pressing shift
KeyUp   (*1) 0000 007A ' ' U+0000 00000030  <-- ??
KeyUp   (*1) 0000 007A ' ' U+0000 00000030  <-- ??
KeyDown (*1) 00DD 001A ' ' U+0000 00000030  <-- pressing ë (w/o e)
KeyUp   (*1) 00DD 001A ' ' U+0000 00000030  <-- releasing everything
KeyUp   (*1) 0010 002A ' ' U+0000 00000020
KeyDown (*1) 0045 0012 '%' U+C589 00000020  <-- pressing e
KeyUp   (*1) 0045 0012 'e' U+0065 00000020  <-- releasing e
--- END SCREEN SNIPPET ---
(I don't have the ^/ë(w/o e) button on my QWERTY keyboard w/ which I'm 
typing this, ofcourse)

If you want more info, just mail - I'm in a helpful mood today :)

Greetz!

Ronald


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2001-09-21  6:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 10:30 Hans-Bernhard Broeker
2001-09-20 10:41 ` Larry Hall (RFK Partners, Inc)
2001-09-20 11:21   ` David Starks-Browning
2001-09-24  4:45     ` Hans-Bernhard Broeker
2001-09-24  7:36       ` Larry Hall (RFK Partners, Inc)
2001-09-20 13:08   ` Jason Tiller
2001-09-20 13:14     ` Larry Hall (RFK Partners, Inc)
2001-09-20 13:39       ` Jason Tiller
2001-09-20 13:57         ` Christopher Faylor
2001-09-20 14:14           ` Jason Tiller
2001-09-20 15:58             ` Marius Gedminas
2001-09-20 16:23               ` Jason Tiller
2001-09-21  4:59                 ` Ronald Landheer
2001-09-20 17:46               ` Gerrit P. Haase
2001-09-21  1:37                 ` Corinna Vinschen
2001-09-25  8:07                   ` Gerrit P. Haase
2001-09-21  6:02               ` Ronald Landheer [this message]
2001-09-21  6:05               ` Ronald Landheer
2001-09-24  5:05   ` Hans-Bernhard Broeker
2001-09-20 14:26 ` Gerrit P. Haase
2001-09-24  4:49   ` Hans-Bernhard Broeker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NFBBLOMHALONCDMPGBLFAEPBCBAA.info@rlsystems.net \
    --to=info@rlsystems.net \
    --cc=cygwin@cygwin.com \
    --cc=marius.gedminas@uosis.mif.vu.lt \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).