WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel][PATCH][qemu-xen]fix '|' key display problem in en-us wit

To: Chun Yan Liu <cyliu@xxxxxxxxxx>
Subject: Re: [Xen-devel][PATCH][qemu-xen]fix '|' key display problem in en-us with altgr processing
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Wed, 5 Jan 2011 12:55:37 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 05 Jan 2011 04:57:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D1248C0020000660001B4EA@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <4D1248C0020000660001B4EA@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2010-12-22 at 07:51 +0000, Chun Yan Liu wrote:
> 
> Changeset 7410 handles altgr-insert problem. Unfortunately, with that
> patch, there is a problem in En-us keyboard: '|' (bar) cannot be
> displayed. After checking keymap files, we found there are two
> definitions to "bar" in en-us:
> bar 0x56 altgr (in "common")
> bar 0x2b shift (in "en-us")
> First line is actually invalid in en-us lanuage. The 2nd definition
> will cover the 1st one.
> 
> Patch in Changeset 7410 didn't consider multi-definition case. It
> scans keymap files, if keysym needs altgr, it will records that, after
> that, if keysym is pressed but altgr not pressed, it will add an altgr
> press opeartion. It is correct if all keysyms are unique and valid.
> But in the above multi-definition case, there is problem: when
> reading 
> bar 0x56 altgr (in "common")
> it will record altgr needed, but in fact, that definition won't be
> used, it always use the 2nd definition and won't need altgr. Then if
> the keysym is pressed, the code will still add an altgr press
> operation, that will cause problem.
> 
> So, if we cannot avoid multi-definition in keymap files, the altgr
> flag (whether altgr needed or not) should also be refreshed according
> to the 2nd defintion. In the above case, when reading the 1st line, it
> records altgr needed; then reading 2nd line, 2nd definition will cover
> the 1st, meanwhile the altgr flag should be reset (the 2nd definition
> doesn't need altgr, so altgr flag should be removed.)
> 
> Following patch supplements patch in Changeset 7410, solve the
> problem. Please share your comments. Thanks!
> 
> Singed-off-by ChunyanLiu <cyliu@xxxxxxxxxx>

Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

This fixes an issue I was seeing with the en-gb keymap too.

Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>