From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: kbd@lists.altlinux.org
Subject: Re: [kbd] 1.15.4 schedule
Date: Sun, 18 Nov 2012 03:35:52 +0400 [thread overview]
Message-ID: <50A81F58.7000002@gmail.com> (raw)
In-Reply-To: <201211171317.09393.vapier@gentoo.org>
17.11.2012 22:17, Mike Frysinger wrote:
> On Saturday 17 November 2012 08:31:57 Alexey Gladkov wrote:
>> I think it's time to make a new release and try new auto-convert
>> feature and other serious changes.
>
> the latest versions have caused problems with default names:
> # loadkeys es
> Loading /usr/share/keymaps/i386/olpc/es.map.gz
> assuming iso-8859-1 diaeresis -> this message could be related
>
> whereas older versions:
> # loadkeys es
> Loading /usr/share/keymaps/i386/qwerty/es.map.gz
>
> we rename the maps in our builds to avoid this:
> cd data/keymaps/i386
> mv dvorak/no.map dvorak/no-dvorak.map
> mv fgGIod/trf.map fgGIod/trf-fgGIod.map
> mv olpc/es.map olpc/es-olpc.map
> mv olpc/pt.map olpc/pt-olpc.map
> mv qwerty/cz.map qwerty/cz-qwerty.map
>
> fedora does the same thing
I know about this bug. This is a big problem across the keymap
directory - the unique names in all tree. For me this is the biggest
problem.
Now I don't want to begin global renaming because it won't solve the
main problem.
I'm currently working on a very large changes in a separate branch. I
hope that these changes will finally resolve this issue and some others.
This release is made to push new utilities and new keymaps and to fix
bugs in the previous release.
--
Rgrds, legion
prev parent reply other threads:[~2012-11-17 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 13:31 [kbd] 1.15.4 schedule Alexey Gladkov
2012-11-17 18:17 ` Mike Frysinger
2012-11-17 23:35 ` Alexey Gladkov [this message]
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=50A81F58.7000002@gmail.com \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.org \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).