Date: Wed, 13 Aug 2014 09:02:56 +0200 From: Stefan Esser <se@freebsd.org> To: Ed Maste <emaste@freebsd.org> Cc: "Andrey V. Elsukov" <ae@freebsd.org>, Aleksandr Rybalko <ray@ddteam.net>, freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Keymap definitions for VT / NEWCONS Message-ID: <53EB0DA0.5000305@freebsd.org> In-Reply-To: <CAPyFy2DMtFhwosD4z4sVHANB3Bp9_kECNrMWHOH=VpJiPyg2aQ@mail.gmail.com> References: <53EA0EC2.2070601@freebsd.org> <53EA1E5A.5020707@FreeBSD.org> <53EA2D00.7010307@freebsd.org> <CAPyFy2DMtFhwosD4z4sVHANB3Bp9_kECNrMWHOH=VpJiPyg2aQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 12.08.2014 um 19:40 schrieb Ed Maste:
> On 12 August 2014 11:04, Stefan Esser <se@freebsd.org> wrote:
>> This is my list of converted keymaps I'm ready to commit:
> ...
>> danish.acc.kbd
>> danish.kbd
>
> I wonder if we should use this opportunity to rationalize the keyboard
> layout names, using two letter codes consistently (so dk.kbd). This
> would also bring consistency with the X11 keyboard layout codes.
Yes, one of the reasons that I did not commit the converted keymaps
as they currently are is naming. I left the old names (without .iso.)
to simplify comparisons, but wanted to normalize them before commit.
I have renamed the files to 2-character ISO country code names, and
have used the form "fr_CH.kbd" (instead of "swisscfrench.iso.kbd")
where there are several locales within a country.
Unresolved:
- Shall keymap names for countries where language and country are
identical (e.g. "pt.kbd") be converted to "pt_PT.kbd"?
(I'd say yes ...)
- In the example of Switzerland, "swissgerman.kbd" becomes "de_CH.kbd".
* Do we want to add "ch.kbd", too?
* Should it be a symlink to one of the other keymap files (the
majority of the Swiss population would use de_CH, I guess)
* What in the case of "pt_PT.kbd" above - shall there also be a
symlink named "pt.kbd"?
- What shall we do with keymaps like "latinamerican.kbd"?
We could install it under one name and symlink (or link) all
the other relevant locale names to this name.
I could use the list of supported locales under share/locale (sans
the encoding suffix) as a minimum list of keyboards to support.
That would imply, that for every locale selected by a user, there
is a matching default keyboard.
What do you think about this?
(I'm going to upload a new TAR file with the modified names, after
some further changes have been performed: The comments in the
keymap files often refer to encodings, that have no meaning after
the conversion to Unicode ...)
And after all these normalizations have been performed:
- How do we deal with accented versions of keymaps?
(Those with ".acc." in their names ...)
- Do we keep all those variants that only differe in the handling
of the Caps-Lock key (which often is mapped to an additional
Control key)?
> We'll already have some churn in rc.conf settings related to screen
> maps / fonts, so this may not be too much of a burden.
Since the names will change anyway (because of the removal of the
encoding, in case NEWCONS is selected), this will not really hurt
us.
I could imagine a mapping file or script, which converts the name
of the keymap from a SYSCONS name to a NEWCONS name. That script
could be used to advise the user to modify rc.conf, or it could
(for the lifetime of 10.x) be invoked from the keymap set script
in rc.d when kbdcontrol failed to set a keymap based on the "old"
name.
Opinions?
Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53EB0DA0.5000305>