Created attachment 33025 [details] [review] A patch for us and ru symbols files. A lot of serbian-talking people live in Russia, and some of them would like to have a possibility to enter serbian language charecters on standard russian keyboards, which do always have US and Russian key labels. A level3 versions of such keyboard layouts included. The charecter mappings are mostly intuitial (to the closest phoneticly corresponding charecter), except for the folliwing: 1. USA - Serbian: 1.1. gachek ("dead_caron") is mapped to [6^] key; 1.2. "dead_acute" is mapped to ['"] 1.3. Euro and cent mapped to ["eE"] (l3); 1.4. nbsp mapped to [Space] (l3); 1.5. "dz with caron" mapped to [zZ] (l3) as [dD] is already occupied by "d with stroke"; 2. Russian - Serbian: 1.1. "dzhe" is mapped to "de" (l3); 1.2. "dje" is mapped to "zhe" (l3).
Could you please update your patch to include the parts for base.xml.in. Do not forget the language code please.
Created attachment 33469 [details] [review] Diff againt xkeyboarg-config 1.8 source The updated diff includes base.xml.in changes with language codes.
Sorry for spamming, but is there anything else I can do to get this patch to the trunk?
(In reply to comment #3) > Sorry for spamming, but is there anything else I can do to get this patch to > the trunk? > (In reply to comment #3) > Sorry for spamming, but is there anything else I can do to get this patch to > the trunk? > Dmitry, sorry, this bug got lost because of the issues with maillist. I am looking at your attachment. It is generally ok. Would you mind if I name the variants as 'srp' - us(srp) and ru(srp)?
Anyway, committed as 2 'srp' variants. If you have objections, please let me know. Thanks a bunch!
(In reply to comment #4) > Dmitry, sorry, this bug got lost because of the issues with maillist. I am > looking at your attachment. It is generally ok. Would you mind if I name the > variants as 'srp' - us(srp) and ru(srp)? Absolutely not. 'us(srp)' and 'ru(srp)' seem perfect to me.
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.