public inbox for kbd@lists.linux.dev
 help / color / mirror / Atom feed
From: Sébastien <eichi237@mailoo.org>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] Include Bépo in the set of default layouts
Date: Sun, 21 Apr 2013 21:36:23 +0200	[thread overview]
Message-ID: <4475142.ayaAJyMfGa@seb-pc> (raw)
In-Reply-To: <517429EA.60702@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]

Le dimanche 21 avril 2013 22:03:22 Alexey Gladkov a écrit :
> 19.04.2013 00:53, Sébastien wrote:
> > Hi,
> > 
> > 
> > I’m french (sorry if I do some mistakes), and I’m using the Bépo keyboard
> > layout. It’s a popular Dvorak-like French-optimized keyboard layout. Some
> > reasons to include it:
> > 
> > – Bépo layout is popular, see the number of people registered on our
> > forum:
> > http://forum.bepo.fr/userlist.php (if we don’t count people with 0
> > messages
> > posted, 33 + 50 × 8 = 433), or on Linuxfr.org:
> > https://linuxfr.org/sondages/la-disposition-b%C3%A9po%E2%80%A6 (203 people
> > claims that they use Bépo, 114 wants to use it and 443 says “maybe one
> > day”). Some of this people created Ergodis, an association to promote
> > Bépo (but not only).
> > 
> > – physical Bépo keyboards. How to install a distro if we can’t use our
> > keyboard? (http://typematrix.com/bepo.php and
> > http://www.ceciaa.com/clavier-ergoneos-fort-contraste-disposition-bepo-c2
> > 391-7.php for example).
> > 
> > – Bépo isn’t available on some distributions, so it’s not easy to install
> > it, especially for “noobs”. Bépo directly in kbd means no maintenance
> > problems for distributions and unified and simple solution to the
> > problem.
> > 
> > – Bépo layout won’t evolve anymore (instead, we want to do a new
> > (perfect?)
> > keyboard layout for the (far?) future). It means no maintenance burden for
> > you. Also, it’s less than 85 KiB (licences included)
> > 
> > 
> > So, what do you think about this idea?
> 
> I have no objections about it.

How do you make decisions here? Anybody is responsible of keyboard layouts?

However, the archive which contains all the files are here:
http://download.tuxfamily.org/dvorak/keymaps/fr-dvorak-bepo-keymaps-1.0rc2.tgz

(Yes it’s RC2, it’s the version we’ve freezed)

P.-S.: In the fr-dvorak-bepo.map, a dev puts a comment:
“CapsLock with '+eacute' doesn't work, nor with egrave, ccedilla,
ecircumflex, agrave and guillemotleft/right : bug ?”
Do you know how to resolve this problem? It’s better to check if everything is 
ok before including it, isn’t it?

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-04-21 19:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 20:53 [kbd] Include Bépo in the set of default layouts Sébastien
2013-04-21 18:03 ` Alexey Gladkov
2013-04-21 19:36   ` Sébastien [this message]
2013-04-22 11:44     ` Alexey Gladkov
  -- strict thread matches above, loose matches on Subject: below --
2013-07-17  8:14 Sébastien
2013-07-30 13:15 ` Alexey Gladkov
2013-08-08 22:15   ` Sébastien
2013-08-13 14:15     ` 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=4475142.ayaAJyMfGa@seb-pc \
    --to=eichi237@mailoo.org \
    --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