Bug 12893 - Komi keyboard layout
Summary: Komi keyboard layout
Status: CLOSED FIXED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: All All
: medium minor
Assignee: xkb
QA Contact:
URL: http://download.gna.org/i18n-komi/kv
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-23 06:47 UTC by Vlad Shakhov
Modified: 2007-10-26 01:13 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Komi language layout (774 bytes, text/plain)
2007-10-23 06:48 UTC, Vlad Shakhov
Details

Description Vlad Shakhov 2007-10-23 06:47:28 UTC
Komi ( also known as Zyrian, or Komi-Zyrianis ) is a language based on cyrillic (russian).  

http://en.wikipedia.org/wiki/Komi_language for details.

The simple layout has been prepared.
Comment 1 Vlad Shakhov 2007-10-23 06:48:35 UTC
Created attachment 12163 [details]
Komi language layout
Comment 2 Sergey V. Udaltsov 2007-10-23 15:44:30 UTC
Thanks, committed as ru(kom)
Comment 3 Vlad Shakhov 2007-10-25 12:22:06 UTC
Please rename the Komi layout to 'kv' (from 'kom')

This language have both Alpha-2 and Alpha-3 ISO 639-2 codes.

Reference: http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes#K 
Comment 4 Sergey V. Udaltsov 2007-10-25 12:29:51 UTC
I won't do it. Because layouts are organized on per-country basis, ISO 3166. There is no such country as Komi.
Comment 5 Vlad Shakhov 2007-10-25 12:44:39 UTC
I mean  xkb_symbols "kv" name or "ru(kv)" in general, if its possible.


As xkb_symbols "os"' and xkb_symbols "tt" in symbols/ru


Comment 6 Sergey V. Udaltsov 2007-10-25 14:38:16 UTC
The general practice I am trying to push is using 3-letter language codes for new variants (see Alpha-3 on the same page). Why is that a big trouble for you?
Comment 7 Vlad Shakhov 2007-10-26 00:30:41 UTC
There are some reasons for it:
* kv is the language part of locale name (kv_RU). I think it better to have single  name both for locale and layout.
* KV - abbreviation for "кыв" - native word meaning "language" in the broad sense of word and the Komi Language in the narrow sense. 

Shortcut "kom" is for territory name ("Коми"), extracted from "Коми кыв"  word-combination. It's a contradictive decision by ISO committee. Because other Alpha-2 and Alpha-3 shortcasts use the same word shortcasts,
Comment 8 Sergey V. Udaltsov 2007-10-26 00:55:07 UTC
> * kv is the language part of locale name (kv_RU). I think it better to have
> single  name both for locale and layout.
Why? They have no relation at all. BTW, the standard practice to use alpha-2 for the language part goes back to the times where there were few supported languages (and may be in a future we'll see locales with 3-letter language part). Alpha-3 was created because 2-letter combination does not provide enough variants for all languages of the world. And for the same reason I prefer using alpha-3.

> * KV - abbreviation for "кыв" - native word meaning "language" in the broad
> sense of word and the Komi Language in the narrow sense.
Well, that's nice - but these identifiers are internal for xkb. Strictly speaking, they should not be user-visible at all. There is base.xml file which provides all necessary user-visible (and translatable) strings. And in that file, you see full 'Komi'.

> Shortcut "kom" is for territory name ("Коми"), extracted from "Коми
> кыв"  word-combination. It's a contradictive decision by ISO committee.
I see your point here. But you should not start fighting it from our humble project. You're mostly welcome to make ISO change the alpha-3 code for Komi - and I'll consider changing it in xkeyboard-config as well.
Comment 9 Vlad Shakhov 2007-10-26 01:07:53 UTC
I understand your position. Thank you for your time and detailed explanation.

It seems that ru(kom) name stay as layout name.
Comment 10 Sergey V. Udaltsov 2007-10-26 01:13:25 UTC
You're mostly welcome. And thanks for understanding my reasons.


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.