Bug 89083 - Add support for Latinamerican Dvorak layout
Summary: Add support for Latinamerican Dvorak layout
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: All All
: high enhancement
Assignee: xkb
QA Contact:
Keywords: i18n, movetoxkc, patch
Depends on:
Reported: 2015-02-11 13:46 UTC by jorgicio
Modified: 2015-04-04 23:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Evdev patch (465 bytes, text/plain)
2015-02-11 13:46 UTC, jorgicio
latam dvorak patch (4.08 KB, patch)
2015-02-11 13:47 UTC, jorgicio
Details | Splinter Review
Evdev patch (465 bytes, patch)
2015-02-11 13:48 UTC, jorgicio
Details | Splinter Review

Description jorgicio 2015-02-11 13:46:55 UTC
Created attachment 113351 [details]
Evdev patch

Hi! I'm Chilean, and I use the Dvorak layout since a few months. However, I had to use the Spanish variant because there's not a Latam variant for that layout.

Based in a work done by a fellow mate[1], I created some patches to apply to some files in the sources:

* evdev-dvorak.patch: for the rules/evdev.xml.in file.
* latam-dvorak.patch: for the symbols/latam file.

I applied both here, and both work. You need only this for supporting the Latam variant for the Dvorak Keyboard. Also tried the layout (with the package patched), and works the same as the Latam QWERTY, but in Dvorak.


[1]: https://github.com/flobosg/latam-dvorak
Comment 1 jorgicio 2015-02-11 13:47:28 UTC
Created attachment 113352 [details] [review]
latam dvorak patch
Comment 2 jorgicio 2015-02-11 13:48:14 UTC
Created attachment 113353 [details] [review]
Evdev patch
Comment 3 Pablo Lezaeta 2015-03-19 23:50:26 UTC
any dev: any new on this enhancement? or the patches need modifications??
or something.

anything us can do you we and viceversa to make this merge into xkb?
Comment 4 Sergey V. Udaltsov 2015-04-04 23:11:43 UTC
thanks, committed. Had to update base.xml.in instead of evdev.xml.in

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.