From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: kbd@lists.altlinux.org
Subject: Re: [kbd] Changing bépo layout name
Date: Wed, 09 Oct 2013 11:37:06 +0400 [thread overview]
Message-ID: <525507A2.5010200@gmail.com> (raw)
In-Reply-To: <24789809-077c-4c17-a0cc-b64b99e7b8e6@email.android.com>
09.10.2013 11:01, sinma wrote:
> Almost everybody in UTF-8, so fr-dvorak-bepo-utf8 might become
> fr-bepo and the non-utf8 map fr-bepo-latin9 (or something that make
> sense).
Ok.
dvorak-fr-bepo-utf8.map -> fr-bepo.map
dvorak-fr-bepo.map -> fr-bepo-latin9.map
> It might also appear in the changelog that the renaming breaks user
> config. I can contact Gentoo and Arch Linux packagers, but other
> distributions may package kbd 2.0 before next release of kbd and I
> can't check all the little distributions.
I'll add this rename into the changelog of course, but I don't think
that many people started using bepo from kbd-2.0.
--
Rgrds, legion
next prev parent reply other threads:[~2013-10-09 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 20:13 [kbd] Changing bépo layout name sinma
2013-10-07 20:20 ` Alexey Gladkov
2013-10-07 23:37 ` Sébastien
2013-10-08 9:49 ` Alexey Gladkov
2013-10-09 7:01 ` sinma
2013-10-09 7:37 ` Alexey Gladkov [this message]
2013-10-09 12:01 ` sinma
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=525507A2.5010200@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