From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] duplicate filenames
Date: Sun, 16 Mar 2008 00:28:24 +0300 [thread overview]
Message-ID: <47DC3F78.4030509@gmail.com> (raw)
In-Reply-To: <577f15290803151142r48ac25cdr3449f3f7bc9a8ad2@mail.gmail.com>
Roman Kyrylych wrote:
> Hi!
>
> I've found that some keymaps' variants have the same filename.
> This is very bad, because doing loadkeys es, for example, will load
> olpc variant which is not what 99,99% of users need. ;-)
Agree. This is really bad problem.
> $ ./find-duplicate-names.sh
> /usr/share/kbd/keymaps/i386/dvorak/no.map.gz
> /usr/share/kbd/keymaps/i386/fgGIod/trf.map.gz
> /usr/share/kbd/keymaps/i386/olpc/es.map.gz
> /usr/share/kbd/keymaps/i386/qwerty/es.map.gz
> /usr/share/kbd/keymaps/i386/qwerty/no.map.gz
> /usr/share/kbd/keymaps/i386/qwerty/trf.map.gz
>
> Please apply the patch attached below.
I shall follow the naming policy when I will add new keymaps.
Something like this: <keyboard_type>-<lang>[-<switch>].map
--
Rgrds, legion
next prev parent reply other threads:[~2008-03-15 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 18:42 [kbd] duplicate filenames Roman Kyrylych
2008-03-15 18:43 ` Roman Kyrylych
2008-03-15 21:28 ` Alexey Gladkov [this message]
2008-03-16 23:00 ` Alexey Gladkov
2009-07-18 17:20 ` Roman Kyrylych
2009-07-21 20:53 ` Alexey Gladkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47DC3F78.4030509@gmail.com \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox