Bug 7069 - Incorrect ABNT2 keyboard layout: key 42 and 45 generates incorrect keysyms
Summary: Incorrect ABNT2 keyboard layout: key 42 and 45 generates incorrect keysyms
Status: RESOLVED INVALID
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2006-05-30 00:34 UTC by Peter Åstrand
Modified: 2010-05-07 12:56 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Screenshot of Layout View and incorrect xmodmap setting (110.65 KB, image/png)
2006-05-30 00:36 UTC, Peter Åstrand
Details

Description Peter Åstrand 2006-05-30 00:34:35 UTC
(Transferred from https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=191732)

The X11 ABNT2 keyboard layout is not quite correct. Two keys are wrong:

* Key 42[*] (keycode 51, the third key to the right of L) should generate
bracketright/braceright/ordfeminine, but currently generates backslash/bar. 

* Key 45[*] (keycode 94, the key to the left of Z) should generate
backslash/bar, but currently generates less/greater/bar. 

[*]: As defined by the MS Keyboard Scan Code Specification. 

xorg-x11-server-Xorg-1.0.1-9.fc5.1.1 and have installed all FC5 updates as of
2006-05-15. 


How reproducible:


Steps to Reproduce:
1. Start GNOME
2. Start Preferences->Keyboard->Layouts. 
3. Select the Brazil ABNT2 model and the Brazil layout. 
  
One additional strangeness is that when using the Keyboard Layout Applet and
selecting Layout View, it shows the correct symbols for these keys. Thus, the
displayed layout does not match the actual layout.
Comment 1 Peter Åstrand 2006-05-30 00:36:57 UTC
Created attachment 5758 [details]
Screenshot of Layout View and incorrect xmodmap setting
Comment 2 Daniel Stone 2007-02-27 01:32:17 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 3 Sergey V. Udaltsov 2009-03-17 03:54:54 UTC
Should be nearly ok now in git. Please check.

key <BKSL>  { [bracketright, braceright,  masculine,    masculine   ] };

key <LSGT>  { [ backslash,        bar,    masculine,   dead_breve ] };

The only thing is that instead of ordfeminine BKSL is mapped (on 3rd and 4th levels) to masculine. The ordfeminine is put on AE11 (after bracketleft/braceleft). Is that ok?
Comment 4 Peter Åstrand 2009-03-17 04:56:53 UTC
<LSGT> is fine. 

>The only thing is that instead of ordfeminine BKSL is mapped (on 3rd and 4th
>levels) to masculine. The ordfeminine is put on AE11 (after
>bracketleft/braceleft)

Any motivation for this? On my physical ABNT keyboard, BKSL has bracketright, braceright, ordfeminine. 
Comment 5 Sergey V. Udaltsov 2009-03-17 09:41:45 UTC
> Any motivation for this? On my physical ABNT keyboard, BKSL has bracketright,
> braceright, ordfeminine. 
Have no idea. As far as I can see, it was there since I started to deal with the project.
Comment 6 Sergey V. Udaltsov 2010-05-06 13:51:14 UTC
That bug (as many others) was hidden by NEEDINFO status. Just to close it - could you please answer a couple of final questions:
1. Could you confirm that most of the keyboards sold in br use ordfeminine?
2. Could you make a photo of that key so I could see the engraving?
Comment 7 Peter Åstrand 2010-05-07 06:30:40 UTC
> 1. Could you confirm that most of the keyboards sold in br use ordfeminine?
> 2. Could you make a photo of that key so I could see the engraving?

To be honest, the topic of this bug is now a little bit outside my focus. It's ok to close the bug.
Comment 8 Sergey V. Udaltsov 2010-05-07 12:56:50 UTC
ok. no problem. Again, my apologies sorry for ignoring this bug.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.