-
-
Notifications
You must be signed in to change notification settings - Fork 260
New Dvorak Layout #1043
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
New Dvorak Layout #1043
Conversation
Julow
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AlexandraAlter What do you think of this Dvorak layout ? You added the initial layout in #16
I'd prefer to keep only one version of the Dvorak layout, if that's OK with you.
| <key key0="м" key7="|" key8="\\" /> | ||
| <key key0="и" key7="~" /> | ||
| <key key0="т" key7="ц" /> | ||
| <key key0="т" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this change ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed that tse because it's not necessary in Tajik. I added it before because it's a common enough cyrillic letter in russian and slavic languages, so I thought it would be better to have than not to have, but now after #1042 , the compose sequences enable you to type ц by compose+т+с so there is no need for an explicit tse in the tajik layout anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks :)
|
The top row though… Even though I shifted it rightward some by adding the explicit period key, it's still too far to the left. For faithfulness to the physical layout's sake, P should be right over U, and L should be right over S. As it is, in my layout, they're still offset, to make room for the backspace. This isn't ideal. Maybe I'll find a sane way to fix it later, but right now I'm just not willing to move that backspace out of the way. |
|
Sorry my screenshot was of the wrong layout (it was the one currently in the app). Thanks for correcting. I think it's a little sad that the backspace key is so small. It's a frequently used key and in the future we might want to do long swipe from it: #46 On a physical layout, the backspace is at the same place on Dvorak and on Qwerty and in the app, the backspace key is at the right of the third row. What do you think of moving it on the third row after the Z key ? By removing the |
|
It's a good thought. I'll contemplate it over the next few days, as I'll be traveling anyway, and we'll see if we might come up with any other solution. What you propose would indeed allow us to fix the top row's issues, but it would create essentially the same issue with the bottom row, becoming at least a full key's width out of alignment with the middle and upper rows. Most mobile layouts can take for granted that the punctuation is in the bottom right, and can therefore be displaced for backspace's sake, but in dvorak, that samu punctuation's on the top left instead, which is just no place for backspace. So it's a bit tougher. Maybe we could modify the bottom row where the spacebar and enter key are. Yeah, maybe a custom bottom row can be backspace's home. Or maybe, we can squeeze an extra key on the right edge of the middle and bottom rows to bring things into alignment — maybe hyphen and backspace, while upper backspace becomes forward-slash. It might make it feel a wee bit more squished though, so I'll test it and see, and I'll contemplate over the next few days. |
|
Yeah, had some issues myself with the current layout. The most ideal top-row felt like it'd involve a backspace on the very left, which is unconventional but felt good to me in the first draft. I use the current layout daily, and still hit backspace too often by accident where it is, and struggle with the keys being out of alignment. The uneven key-widths at the top do throw me a little, but I think that's just personal preference. Sadly, I do still feel like a larger BS and Shift key would be better. A few of the key placements (delete, tab, numeric symbols, comma) do feel strange to me. I feel like there may be a more commonly used symbol to place on the semicolon key, such as the quote mark. I like how the brackets are placed on opposite corners. I might draft up other options, too. Am I right in thinking that the main thing we want to fix is key alignment? |
|
New iteration, featuring larger shift and larger backspace, better row alignments, and three additional keys. The keys are a bit thinner now than they were before, but they're pretty much the same width as the current persian layout's keys are, so it's not without precedent. I've been testing it a few days. It works pretty well, and it's not hard to get used to. However, it will take a bit of getting used to for anybody who's used to the existing dvorak layout. Because the row alignment is quite different now than in was. It's a lot closer to the intended alignment though, so it's a good change. |
|
You were right, I really hated the misalignment. So I took some time to come up with a different approach. The main thing is that I moved the Z down to the bottom row. That made room for the backspace, and it's not so bad since Z is an uncommon character, and it's a fairly common approach for touch keyboards. Now row alignment is pretty good, and the keys are wider because they have more room to expand into. I don't know exactly how I'll get this committed in a wee while. Work is crazy these days. I gotta get to my computer in my office and then I'll commit it. What do y'all think? |
|
Regarding But I want to swap it back. That key is semicolon's rightful place. What do y'all think? Switch it back? |





Yeah, so this new version of the Dvorak layout is a lot better. The alignment between the rows is way more natural and closer to how it is on actual keyboards. Certain punctuation keys are just more accessible this way too. I encourage replacing the existing one with this one, but I prepared it as an alternate version instead for now, in case there's any reason to hold on to the old one. So they can exist side-by-side.