[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: consistent keyboard config

On Wed, 17 Sep 1997, Marco d'Itri wrote:

> On Sep 16, Christian Schwarz <schwarz@monet.m.isar.de> wrote:
> While I was offline last week I wrote a draft that discuss all keyboard
> problems (except X), I'll post it ASAP (the next week, I hope).


>  >So I think we should stay with m4 for a while, since it's actually
>  >working well. If the functionality of the m4 macros have stabilized, we
> Not really, we must find an m4 guru to resolve some minor issues.

Well, this changes things a bit I think. Since a perl script with the
functionality would be IMHO very easy, I wouldn't look for a "m4 guru"
(how do these people look like? 8-) since we (at least I got the
impression from this discussion) don't like m4 too much, altogether.

So maybe we should collect all requirements for the configuration files
and how the output should be generated. The script should be actually very
easy after that.

What features are you missing from the current m4 macros?

>  >One problem: Some German keyboards have some extra characters assign to
>  >the keys when using the "AltGr" modifier. AFAIK, these chars do not
> The Italian keyboard does that too. If some German keyboards don't have
> that keys the admin will just reassign the altgr key to the alt or hyper
> modifier.

I think we are talking about different things here. (My explanation wasn't
really good--let me try again.) Most keyboards here have the "AltGr" keys,
but some keyboards only "print" the most important AltGr-chars (i.e. chars
you get by using the AltGr modifier together with the key) on the

For example, my keyboard uses "{" for AltGr-7 and "²" for AltGr-2, though 
I've seen keyboards that don't have a key for "²" printed on the board. So
if we define a special meaning for AltGr-4 now (which is not specified on
my keyboard) we'll might get conflicts with other keyboards.

(Maybe this isn't such a big problem.)

>  >can be done! So I think it would be great if we could keep such things
>  >variable for the different users. (I think we should write some kbd-config
> My draft mandates that (s/users/systems/).

Of course, this is what I meant :-)

>  >script which asks some questions and generates a /etc/kbd.conf file.)
> I also wrote some lines about a format for embedding informations in the maps.
> The only think is missing (apart better macros) is the configuration program.
> You should ask kbd maintainer if he can improve it, otherwise we will
> have to find someone.

I'd say we define the config files first. This way, people can start using
our setup by editing the config files "by hand". If everything has
stabilized and we know which features are required, someone could
implement the UI.

>  >Therefore, it would be necessary to hack the readline source to check use
>  >/etc/inputrc unless ~foo/.inputrc exists. Do we have a volunteer here that
>  >wants to checkout the details?
> First ask the maintainer.

Ok, I'll email Guy about this.



--                  Christian Schwarz
                     schwarz@monet.m.isar.de, schwarz@schwarz-online.com,
Debian is looking     schwarz@debian.org, schwarz@mathematik.tu-muenchen.de
for a logo! Have a
look at our drafts     PGP-fp: 8F 61 EB 6D CF 23 CA D7  34 05 14 5C C8 DC 22 BA
at    http://fatman.mathematik.tu-muenchen.de/~schwarz/debian-logo/

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-i18n-request@lists.debian.org . Trouble? 
e-mail to templin@bucknell.edu .

Reply to: