Mac Style "Dvorak - Qwerty Command" keyboard mapping for Windows?

Question

I would be interested in switching to Dvorak keyboard layout. The problem that everyone runs into is that common programming* keyboard shortcuts, such as:

• Ctrl+C
• Ctrl+V
• Ctrl+Z

Will no longer be the keys on the bottom left of the keyboard, since the Dvorak layout has C, V and Z in different locations.

The Mac has solved this problem by having a keyboard layout called "Dvorak - Qwerty Command", where the keyboard is normally in Dvorak mode, but if you press a command key the mappings temporarily revert to Qwerty.

Does such a feature exist on Windows? It has been suggested that such a feat can be accomplished using the Microsoft Keyboard Layout Creator, but I won't pretend to understand all that.

In other words, Stackoverflow users, is this a problem that has already been solved?

---

* The joke being that the most common programming tasks are Ctrl+C, Ctrl+V.

Ablative

I tried using Dvorak-Qwerty when I got into the "hey, let's try Dvorak" phase, and the muscle memory clash gave me a solid headache. Also, MSKLC is actually fairly easy to use. – Commons

I think this belongs on SuperUser.com – Bimah

280Z28: It's never too late ;) – Bimah

My clever way of making it a programming question was that programmers only ever use Ctrl+C, Ctrl+V – Ablative

I have a gamers mouse and bind the most used shortcuts to the buttons on it(ctrl+c, ctrl+v). In fact I even have Ctrl mapped to a key. The mouse must be configured in Windows but also works in Linux if you buy the right one. Different solution but similar problem. – Mcniel

github.com/kentonv/dvorak-qwerty – Mcniel

Answer 1

This can help: https://sourceforge.net/projects/dvorakqwerty/

Mantellone

Answer 2

I use Dvorak exclusively now, including all shortcuts. Here's how and why I got where I am:

I started the change shortly into Christmas break 2.5 years ago. I wasn't in school or work for a bit, so poor typing abilities wouldn't negatively affect my day-to-day activities. I made a pact with myself: no QWERTY, at all, until my Dvorak typing reaches my current QWERTY abilities. That was by far the best and most painful decision. Every day I spent 2-3 hours training for the keyboard. It took 3 weeks to reach 50WPM, and for some reason I capped out there for like 2 months! I kept training, and about 3 months in I surpassed my original normalized efficiency (counts accuracy) from when I used QWERTY. Now I'm marginally faster than when I used QWERTY, but more than anything I've found that my hands no longer hurt at the end of a long day. It makes all the difference in the world.

Rules:

• DO NOT rearrange the keys on your keyboard. It's touch typing, stop looking! Moving the keys messes up the critical f/j hints and changes the keyboard feel, all to provide you with visual information you'll never use.
• DO NOT switch back to QWERTY while you are initially learning Dvorak "so you can get something typed faster."
• DO practice every day with an online typing software. It's been a long time and unfortunately I don't remember where I was practicing. :(
• Initially your fingers will hurt after typing on Dvorak. I had lots of problems with the l key initially, but it was because I simply wasn't used to it and the pressure of learning kept me tense. Things will get better as you improve, and before you know it you'll be more comfortable on Dvorak than you were on QWERTY.

Suggestions:

• DO NOT use the Dvorak/QWERTY combo mode like you mentioned above. Dvorak Assistant lets you use Dvorak wherever you want, and to keep shortcuts consistent for you personally between computers, use the same shortcut characters (in their new locations).

Observation:

• Since it's so much easier for peoeple to learn Dvorak first, and it results in fewer injuries later in life, why on earth aren't we teaching this in our elementary schools??? I honestly believe that it is incorrect to teach "proper typing" to these students with them sitting behind a QWERTY layout. On top of that, the classes already put stickers over all the keys to prevent peeking, so really what is the point of teaching QWERTY? I suppose I'm frustrated because my instructed touch typing on QWERTY is the primary reason it took me so long to learn typing on a real keyboard later.

Presurmise

Your rules are spot-on (I started learning Dvorak a year ago and came to the same conclusions as you did). I used this awesome website to learn typing Dvorak (it has multiple languages also). However, I disagree about the cmd-qwerty/dvorak thing. I find it extremely helpful, and it doesn't cause any dvorak/qwerty clashes. Plus, without it, you can't do cmd+c or cmd+x with one hand easily. But, they REALLY should teach Dvorak (or any other decent non-QWERTY layout) in schools... It's a shame no one even knows about anything other than QWERTY... – Yazbak

On second thought, after trying Kenton's tool for Linux, I can see your point. It is a little confusing for me now to use the dvorak/qwerty shortcut tool (I can see myself getting used to it, though). But I do suggest that people try both and check them out... – Yazbak

C am gocbi a ,.xocy...I mean, I am learning Dvorak through a site called PowerTyping. They also have a QWERTY course. – Roose

I also think it's worth mentioning that Android phones allow you to add custom keyboard layouts, such as Dvorak You also can do it on iPhone, but it requires you to jailbreak. – Roose

I switched 12 years ago, and this post is exactly how I did it as well, I trained 2 hours a night using online typing games... shooting letters out of the sky, etc :-) – Italia

Answer 3

I was in the same situation, so I wrote this:

http://dvorak-qwerty.googlecode.com

Hope it helps!

(Maybe using the keyboard layout creator would be better but I didn't want to figure it out either!)

Precipitant

I don't recommend the "dverty" layout linked off this page -- when caps lock is on, it leaves the 's', 'v', and 'w' characters lowercase. – Diffuser

Does your code work on Ubuntu? I seemed to have trouble with #include <X11/Xlib.h> with the error report that no such file exists. But it looks like this library is specific to Mac OS X – Merari

Answer 4

AutoHotKey to the rescue. This will use DVORAK when typing normally and when holding Shift. While Ctrl or Alt is held down QWERTY behaviour takes over.

;Sorry about the messed up syntax highlighting.
;Disclaimer: may not work at all.
#UseHook
-::Send {Blind}[
=::Send {Blind}]

q::Send {Blind}'
w::Send {Blind}`,
e::Send {Blind}.
r::Send {Blind}p
t::Send {Blind}y
y::Send {Blind}f
u::Send {Blind}g
i::Send {Blind}c
o::Send {Blind}r
p::Send {Blind}l
[::Send {Blind}/
]::Send {Blind}=

a::Send {Blind}a
s::Send {Blind}o
d::Send {Blind}e
f::Send {Blind}u
g::Send {Blind}i
h::Send {Blind}d
j::Send {Blind}h
k::Send {Blind}t
l::Send {Blind}n
`;::Send {Blind}s
'::Send {Blind}-

z::Send {Blind}`;
x::Send {Blind}q
c::Send {Blind}j
v::Send {Blind}k
b::Send {Blind}x
n::Send {Blind}b
m::Send {Blind}m
,::Send {Blind}w
.::Send {Blind}v
/::Send {Blind}z

;capitalise

+-::Send {Blind}{{}
+=::Send {Blind}{}}
+q::Send {Blind}"
+w::Send {Blind}<
+e::Send {Blind}>
+r::Send {Blind}P
+t::Send {Blind}Y
+y::Send {Blind}F
+u::Send {Blind}G
+i::Send {Blind}C
+o::Send {Blind}R
+p::Send {Blind}L
+[::Send {Blind}?
+]::Send {Blind}{+}

+a::Send {Blind}A
+s::Send {Blind}O
+d::Send {Blind}E
+f::Send {Blind}U
+g::Send {Blind}I
+h::Send {Blind}D
+j::Send {Blind}H
+k::Send {Blind}T
+l::Send {Blind}N
+;::Send {Blind}S
+'::Send {Blind}_

+z::Send {Blind}:
+x::Send {Blind}Q
+c::Send {Blind}J
+v::Send {Blind}K
+b::Send {Blind}X
+n::Send {Blind}B
+m::Send {Blind}M
+,::Send {Blind}W
+.::Send {Blind}V
+/::Send {Blind}Z

Eventually this may become a shot in the foot because it cannot be used with GNU/Linux, so another solution may be required if you ever try it out.

Summarize

FYI: This script is meant to be used on a QWERTY layout. If you use it on the DVORAK layout, insanity will ensue. – Nomenclature

Answer 5

Dvertkey, an AutoHotKey script, caters for more scenarios than any other Windows solution I've used.

This is an old question, but I've kept coming back here over the years and no solution has been without annoyances. Thanks to ftvs for the AutoHotKey answer that inspired me to write this script.

I've been a dvorak user for sixteen years, and for years I've used the various alternative keymaps mentioned in this thread, but all of them fall down when using a number of recent incarnations of Microsoft applications, such as the Office apps and SQL Server Management Studio. They seem to ignore Windows' own keymaps when using meta keys, rendering the hybrid layouts useless. AutoHotKey gets around this to ensure I get exactly what I want in any application.

While I agree with the sentiment of Sam Harwell's advice for new dvorak users, I disagree with the suggestion of not changing shortcut characters. Good keyboard shortcuts are about their positions on the keyboard more than the character that represents it. These are often chosen with good reasons (eg. the common X C V being cut-copy-paste, together at the bottom of the keyboard) and there's no reason to lose that good shortcut positioning when moving to Dvorak. This script will retain that.

Wadesworth

Answer 6

You're right, AutoHotkey doesn't help GNU/Linux users...but, if you're on Windows, AutoHotkey once again comes through! Except that the code should be more like this:

^;::Send {Blind}z   ;Undo
^q::Send {Blind}x   ;Cut
^j::Send {Blind}c   ;Copy
^k::Send {Blind}v   ;Paste
^o::Send {Blind}s   ;Save
^r::Send {Blind}o   ;Open
^f::Send {Blind}y   ;Redo

I had a feeling that AHK was the answer, but I didn't know how to go about doing it. Thanks for pointing me in the right direction!

Skatole

Answer 7

You can try this http://aming-blog.blogspot.com/2010/10/mac-style-dvorak-qwerty-control-layout.html

Jeddy