public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: Paul Maier <svn-user@web.de> Cc: 'cygwin-xfree' <cygwin-xfree@cygwin.com> Subject: Re: AW: 'de' keyboard layout issues (Re: AW: AW: AltGr key mostly fires an additional CONTROL key) Date: Wed, 10 Aug 2011 12:12:00 -0000 [thread overview] Message-ID: <4E4275B4.9090906@dronecode.org.uk> (raw) In-Reply-To: <001c01cc5621$4ae653e0$e0b2fba0$@de> [-- Attachment #1: Type: text/plain, Size: 2863 bytes --] On 09/08/2011 00:17, Paul Maier wrote: > 1. Tilde sign > ------------- > >>> Tilde sign (~) should be a normal (not a blind) key. >>> In Windows I hit AltGr+"+" to get ~, in XWin I need to type AltGr+"+" then space to >> get a ~. >>> See attachment for the initial XWin xmodmap -pke table. >>> Possible xmodmap correction (works fine): >>> keycode 35 = plus asterisk plus asterisk asciitilde >> >> This is a can of worms I don't want to open :-) In case it wasn't clear, the can of worms here is ensuring that XWin selects a keyboard layout which matches the Windows one in all cases. >> At the moment, in the 'de' layout, the tilde deadkey will add a macron >> diacritic, e.g. AltGr + "+" + a = ã. Obviously I meant to write 'tilde diacritic' here :-) >> I really lack the expertise to determine if this is a bug in xkeyboard-config >> (if this german keyboard behavior is something no german keyboard user would >> ever expect or want) >> >> The xkb configurations we use come from the xkeyboard-config project, and >> aren't trying to be identical to Windows, but to conform to the appropriate >> national standards and user expectations. >> >> However, I can see in the case of XWin this is problematic, as it will be >> confusing to switch between X and normal Windows windows which have different >> keyboard behavior. > > I did some research: German computer keyboard layout is defined in DIN 2137-2. > And to my surprise I found, that tilde is a dead key there. > That means, that the xkeyboard-config project perfectly matches the DIN norm, > while Windows (where the key is not dead) does not match it. > So I understand, that you may want to stick to the DIN norm. Usability comes before standards compliance :-) > A workaround for guys like me, who want the XWin keyboard work the same like Windows, > is possible with xmodmap, so yeah ... let's close this point. Doing some more research, I found an upstream bug [1], which seems to make the opposite claim about DIN 2137-2(1998) I also discovered that the nodeadkeys variant of the de layout was at one stage the default used by XWin when a German Windows keyboard layout was reported [2] Maybe the 'correct' solution is possibly to create a 'nodeadtilde' variant of the de layout in xkeyboard-config, and then to arrange for that to be the default used by XWin when Windows reports a German keyboard layout. Perhaps you'd like to try the attached patch to /usr/share/X11/xkb/symbols/de, which adds a nodeadtilde variant, which you can then select with -xkbvariant nodeadtilde. Or perhaps the correct solution is to use one of the existing deadgraveacute or deadacute variants as the XWin default when Windows reports a German keyboard layout? [1] https://bugs.freedesktop.org/show_bug.cgi?id=9752 [2] http://cygwin.com/ml/cygwin-xfree/2003-05/msg00495.html [-- Attachment #2: de.patch --] [-- Type: text/plain, Size: 582 bytes --] --- de.old 2011-08-09 20:17:57.406250000 +0100 +++ de 2011-08-09 20:26:52.156250000 +0100 @@ -96,6 +96,17 @@ }; partial alphanumeric_keys +xkb_symbols "nodeadtilde" { + // modify the basic German layout to not have the tilde dead key + + include "de(basic)" + + name[Group1]="German (nodeadtilde)"; + + key <AD12> { [ plus, asterisk, asciitilde, macron ] }; +}; + +partial alphanumeric_keys xkb_symbols "ro" { // add romanian-specific letters to the basic German layout. // Romanian symbols are accessible with combination of <AltGr> and [-- Attachment #3: Type: text/plain, Size: 223 bytes --] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2011-08-10 12:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <006301cc4fb3$2696d060$73c47120$@de> 2011-08-01 14:57 ` AltGr key mostly fires an additional CONTROL key Jon TURNEY [not found] ` <000001cc5085$6b711fb0$42535f10$@de> 2011-08-03 13:15 ` AW: " Jon TURNEY 2011-08-04 2:22 ` AW: " Paul Maier 2011-08-08 15:32 ` 'de' keyboard layout issues (Re: AW: AW: AltGr key mostly fires an additional CONTROL key) Jon TURNEY 2011-08-08 23:17 ` AW: " Paul Maier 2011-08-10 12:12 ` Jon TURNEY [this message] 2011-08-12 6:49 ` Paul Maier 2011-08-16 13:10 ` Jon TURNEY 2011-10-03 11:29 ` AW: AW: 'de' keyboard layout issues Paul Maier 2012-08-06 12:49 ` Jon TURNEY 2012-07-22 0:22 ` Paul Maier 2012-08-06 12:22 ` AW: 'de' keyboard layout issues (Re: AW: AW: AltGr key mostly fires an additional CONTROL key) Jon TURNEY 2011-10-03 10:16 ` AW: AW: AltGr key mostly fires an additional CONTROL key Paul Maier
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=4E4275B4.9090906@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=svn-user@web.de \ /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: linkBe 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).