After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 375801 - does not recognize dvorak keyboard layout for shortcuts
does not recognize dvorak keyboard layout for shortcuts
Status: RESOLVED DUPLICATE of bug 171075
Product: tomboy
Classification: Applications
Component: General
unspecified
Other All
: Normal normal
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-16 04:33 UTC by Daniel F
Modified: 2008-02-26 20:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Daniel F 2006-11-16 04:33:28 UTC
Please describe the problem:
I am using the dvorak keyboard layout. In this layout, for instance, the QWERTY key "b" is actually "x", and the QWERTY key "i" is actually "c". 

So, for example, when I select some text in a note, and type 'control-c' to copy some text, it thinks i am using qwerty, and interprets it as 'control-i', and instead just makes it italic. Similarly, when i select some note text and want to cut it using 'control-x', it thinks i am using qwerty, and interprets it as 'control-b', and instead makes it bold. 

Steps to reproduce:
1. set keyboard layout to dvorak
2. select some text in a note
3. type 'control-x' [using the dvorak layout], and watch it be interpreted as 'control-b' instead.


Actual results:
this should be clear from the above description

Expected results:
this should be clear from the above description

Does this happen every time?
yes

Other information:
every other gnome app has no problem recognizing the keyboard layout being used. so my guess is that tomboy is just hard-coding some shortcuts in ignorance of the kb layout, instead of using some "standard" gnome way that takes into account the layout. so it "should" be easy to fix :)
Comment 1 Jan Alonzo 2007-02-07 06:01:26 UTC

*** This bug has been marked as a duplicate of 171075 ***