Bug 96578 - Update to cm (Cameroon) layout Mmuock
Summary: Update to cm (Cameroon) layout Mmuock
Status: RESOLVED FIXED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: All All
: medium enhancement
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-18 13:31 UTC by Tano Fotang
Modified: 2016-09-15 00:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
diff -u cm-new cm: Update to cm(mmuock) (11.53 KB, patch)
2016-06-18 13:31 UTC, Tano Fotang
Details | Splinter Review
diff -u base.xml-new base.xml (604 bytes, patch)
2016-06-18 13:38 UTC, Tano Fotang
Details | Splinter Review

Description Tano Fotang 2016-06-18 13:31:56 UTC
Created attachment 124587 [details] [review]
diff -u cm-new cm: Update to cm(mmuock)

This is an update to the mmuock keyboard in the cm file. This version 1.2 contains the following changes:
1- added dead keys dead_macron, dead_acute, and dead_grave for
   tones 1, 3, and 4, for compatibility with the Keyman version.
2- rearranged combining diacritics for tones 0 to 5 such that
   the diacritics are on consecutive keys (AC01 to AC05).
3- moved tone 8 to level 3 of AE12.
4- moved layout definition out of the EXTRAS section.
5- for a cleaner keyboard, replaced ṭhe included latin layout with us(basic).
6- corrected typos in previous comments.
Comment 1 Tano Fotang 2016-06-18 13:35:37 UTC
Comment on attachment 124587 [details] [review]
diff -u cm-new cm: Update to cm(mmuock)

This diff was taken on openSuSE Leap 42.1. The cm file that came with the OS, is the same as that on Ubuntu 16.04.
Comment 2 Tano Fotang 2016-06-18 13:38:51 UTC
Created attachment 124588 [details] [review]
diff -u base.xml-new base.xml

This diff was taken on openSuSE leap 42.1 where base.xml carries the date of Oct 25, 2015.
Comment 3 Sergey V. Udaltsov 2016-09-15 00:03:37 UTC
Thanks, committed to git


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.