Summary: | target key highlighting according to qwerty when in colemak layout/lesson | ||
---|---|---|---|
Product: | [Applications] ktouch | Reporter: | hikingpete <hikingpete> |
Component: | general | Assignee: | Haavard Froeiland <haavard> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | albuseer, bugzilla.kde, cryptooctoploid, diwaker.lists, mail, maximsch2, vcunat |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
working Colemak layout for ktouch
full ascii colemak layout fot ktouch |
Description
hikingpete
2008-10-18 01:33:01 UTC
Same problem with ktouch from kde 4.2.1 on gentoo. colemak.keyboard.xml should be fixed to resolve this bug. One way is to get colemak.keyboard from archive here: http://colemak.com/KTouch then open it in ktouch keyboard editor and save in new format without changes. I replaced colemak.keyboard.xml with generated file and problem disappeared. Created attachment 32892 [details]
working Colemak layout for ktouch
Any plans for getting this fixed soon? Confirmed on Ubuntu Jaunty (9.04) too. Can someone update the bug status, please. Thank you. Still the same problem with 4.2.4 on Gentoo. Created attachment 52106 [details]
full ascii colemak layout fot ktouch
Here is another one colemak keyboard.xml, but with full ASCII
I think it should placed to the svn.
How do you think?
*** Bug 218296 has been marked as a duplicate of this bug. *** *** Bug 253001 has been marked as a duplicate of this bug. *** SVN commit 1222486 by annma: fix Colemak keyboard layout in trunk, thanks to Peter Rüthemann REVIEW=6523 CCBUG=173074 CCMAIL=peter.ruethemann@gmail.com M +37 -36 colemak.keyboard.xml WebSVN link: http://websvn.kde.org/?view=rev&revision=1222486 SVN commit 1222488 by annma: backport of 1222486 BUG=173074 M +37 -36 colemak.keyboard.xml WebSVN link: http://websvn.kde.org/?view=rev&revision=1222488 *** Bug 182382 has been marked as a duplicate of this bug. *** |