freebsd-dev/share/vt/keymaps/INDEX.keymaps

607 lines
18 KiB
Plaintext
Raw Normal View History

Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
# $FreeBSD$
#
# database for kbdmap(8)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
#
# Format <file>:<lang>:<description>
#
# lang: ar bg cs da de el en es fi fr he hr hu hy is it ja kk ko nl no pl
# pt ro ru sh sk sl sv tr uk zh
# lang: lang,lang
#
# If lang empty use 'en' (us-english) as default.
#
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
# Example:
# german.iso.kbd:de:deutsch
# german.iso.kbd:en:german
#
# See also setlocal
# /usr/share/locale, /usr/local/lib/X11/locale/locale.alias
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
#
#
# Language support: MENU, FONT
#
MENU:en:Choose your keyboard layout
MENU:da:Vælg dit tastaturlayout
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
MENU:de:Wählen Sie Ihre Tastaturbelegung
MENU:fr:Choisissez la disposition de votre clavier
MENU:no,sv:Vælg dit keyboard layout
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
MENU:pl:Wybierz układ klawiatury
MENU:pt:Escolha o layout do teclado
MENU:es:Seleccione la disposición de su teclado
MENU:he:ךלש תדלקמה תפש תא רחב
MENU:uk:Оберiть розкладку клавіатури
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
MENU:el:Επιλέξτε το πληκτρολόγιο της κονσόλας
MENU:hy:Ընտրեք ստեղնաշարի դասավորությունը
MENU:tr:Klavye düzeninizi seçiniz
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
#
# The font definition for "en" is the fall-back font for
# all languages.
# Add language specific font definitions only where required!
#
FONT:en:vgarom-8x16.hex
#
am.kbd:en:Armenian phonetic layout
am.kbd:da:Armensk fonetisk layout
am.kbd:de:Armenische phonetische Tastenbelegung
am.kbd:fr:Arménien phonétique
am.kbd:hy:Հայերեն հնչյունային (Phonetic) դասավորություն
am.kbd:ru:Армянская фонетическая раскладка
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
be.kbd:en:Belgian
be.kbd:da:Belgisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
be.kbd:de:Belgisch
be.kbd:fr:Belge
be.kbd:pt,es:Belga
be.acc.kbd:en:Belgian (accent keys)
be.acc.kbd:da:Belgisk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
be.acc.kbd:de:Belgisch (mit Akzenten)
be.acc.kbd:fr:Belge (avec accents)
be.acc.kbd:pt:Belga (com acentos)
be.acc.kbd:es:Belga (con acentos)
bg.bds.kbd:en:Bulgarian (BDS)
bg.bds.kbd:da:Bulgarsk (BDS)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
bg.bds.kbd:de:Bulgarisch (BDS)
2014-08-21 20:33:09 +00:00
bg.phonetic.kbd:en:Bulgarian (Phonetic)
bg.phonetic.kbd:da:Bulgarsk (fonetisk)
2014-08-21 20:33:09 +00:00
bg.phonetic.kbd:de:Bulgarisch (phonetisch)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
br.kbd:en:Brazilian (accent keys)
br.kbd:da:Brasiliansk (accenttaster)
br.kbd:de:Brasilianisch (mit Akzenten)
br.kbd:fr:Brésilien (avec accents)
br.kbd:pt:Brasileiro (com acentos)
br.kbd:es:Brasileño (con acentos)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
br.noacc.kbd:en:Brazilian (without accent keys)
br.noacc.kbd:da:Brasiliansk (ingen accenttaster)
br.noacc.kbd:de:Brasilianisch (ohne Akzente)
br.noacc.kbd:fr:Brésilien (sans accents)
br.noacc.kbd:pt:Brasileiro (without accent keys)
br.noacc.kbd:es:Brasileño (without accent keys)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
by.kbd:en:Belarusian
by.kbd:da:Hviderussisk
by.kbd:de:Weißrussisch
by.kbd:fr:Biélorusse
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
centraleuropean.kbd:en:Central European
centraleuropean.kbd:da:Centraleuropæisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
centraleuropean.kbd:de:Zentral Europäisch
centraleuropean.kbd:fr:Centre européen
centraleuropean.kbd:es:Centroeuropeo
centraleuropean.qwerty.kbd:en:Central European (QWERTY)
centraleuropean.qwerty.kbd:da:Centraleuropæisk (QWERTY)
centraleuropean.qwerty.kbd:de:Zentral Europäisch (QWERTY)
centraleuropean.qwerty.kbd:fr:Centre européen (QWERTY)
centraleuropean.qwerty.kbd:es:Centroeuropeo (QWERTY)
colemak-dh.acc.kbd:en:Colemak Mod-DH ergonomic alternative
2014-08-21 20:33:09 +00:00
colemak.acc.kbd:en:Colemak ergonomic alternative
colemak.acc.kbd:da:Colemak ergonomisk alternativ
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
cz.kbd:en:Czech (QWERTZ, accent keys)
cz.kbd:da:Tjekkisk (QWERTZ, accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
cz.kbd:de:Tschechisch (QWERTZ, mit Akzenten)
cz.kbd:fr:Tchèque (QWERTZ, avec accents)
cz.kbd:es:Checo (QWERTZ, con acentos)
dk.kbd:en:Danish
dk.kbd:da:Dansk
dk.kbd:de:Dänisch
dk.kbd:fr:Danois
dk.kbd:pt:Dinamarquês
dk.kbd:es:Danés
dk.acc.kbd:en:Danish (accent keys)
dk.acc.kbd:da:Dansk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
dk.acc.kbd:de:Dänisch (mit Akzenten)
dk.acc.kbd:fr:Danois (avec accents)
dk.acc.kbd:pt:Dinamarquês (com acentos)
dk.acc.kbd:es:Danés (con acentos)
dk.macbook.kbd:en:Danish (MacBook)
dk.macbook.kbd:da:Dansk (MacBook)
dk.macbook.kbd:de:Dänisch (MacBook)
dk.macbook.kbd:fr:Danois (MacBook)
dk.macbook.kbd:pt:Dinamarquês (MacBook)
dk.macbook.kbd:es:Danés (MacBook)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
nl.kbd:en:Dutch (accent keys)
nl.kbd:da:Nederlandsk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
nl.kbd:de:Holländisch (mit Akzenten)
nordic.asus-eee.kbd:en:Nordic layout on Asus eeePC
nordic.asus-eee.kbd:da:Nordisk layout på Asus eeePC
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
nordic.asus-eee.kbd:fr:Norvégien phonétique sur Asus eeePC
ee.kbd:en:Estonian
ee.kbd:da:Estisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ee.kbd:de:Estnisch
ee.kbd:fr:Estonien
ee.kbd:es:Estonio
fi.kbd:en:Finnish
fi.kbd:da:Finsk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
fi.kbd:de:Finnisch
fi.kbd:fr:Finlandais
fi.kbd:es:Finlandés
fr.kbd:en:French
fr.kbd:da:Fransk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
fr.kbd:de:Französisch
fr.kbd:fr:Français
fr.kbd:pt:Francês
fr.kbd:es:Francés
fr.kbd:uk:Французька
fr.acc.kbd:en:French (accent keys)
fr.acc.kbd:da:Fransk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
fr.acc.kbd:de:Französisch (mit Akzenten)
fr.acc.kbd:fr:Français (avec accents)
fr.acc.kbd:pt:Francês (com acentos)
fr.acc.kbd:es:Francés (con acentos)
fr.acc.kbd:uk:Французька (accent keys)
fr.macbook.kbd:en:French (MacBook/MacBook Pro) (accent keys)
fr.macbook.kbd:da:Fransk (MacBook/MacBook Pro) (accenttaster)
fr.macbook.kbd:de:Französisch (MacBook/MacBook Pro) (mit Aksenten)
fr.macbook.kbd:fr:Français (MacBook/MacBook Pro) (accent keys)
fr.macbook.kbd:pt:Francês (MacBook/MacBook Pro) (com acentos)
fr.macbook.kbd:es:Francés (MacBook/MacBook Pro) (con acentos)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
fr.dvorak.kbd:en:French Dvorak-like
fr.dvorak.kbd:da:Fransk Dvorak-lignende
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
fr.dvorak.kbd:de:Französisch Dvorak
fr.dvorak.kbd:fr:Français Dvorak
fr.dvorak.kbd:pt:Francês Dvorak
fr.dvorak.kbd:es:Francés Dvorak
fr.dvorak.kbd:uk:French Dvorak-like
fr.dvorak.acc.kbd:en:French Dvorak-like (accent keys)
fr.dvorak.acc.kbd:da:Fransk Dvorak-lignende (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
fr.dvorak.acc.kbd:de:Französisch Dvorak (mit Akzenten)
fr.dvorak.acc.kbd:fr:Français Dvorak (accent keys)
fr.dvorak.acc.kbd:pt:Francês Dvorak (com acentos)
fr.dvorak.acc.kbd:es:Francés Dvorak (con acentos)
fr.dvorak.acc.kbd:uk:French Dvorak-like (accent keys)
2014-08-18 17:10:55 +00:00
ca.kbd:en:Canadian Bilingual
ca.kbd:da:Canadisk tosproget
2014-08-18 17:10:55 +00:00
ca-fr.kbd:en:French Canadian (accent keys)
ca-fr.kbd:da:Franskcanadisk (accenttaster)
ca-fr.kbd:de:Französisch Kanada (mit Akzenten)
ca-fr.kbd:fr:Français Canadien (avec accents)
ca-fr.kbd:es:Francocanadiense (con acentos)
ca-fr.kbd:uk:Французько-канадська (accent keys)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
de.kbd:en:German
de.kbd:da:Tysk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
de.kbd:de:Deutsch
de.kbd:fr:Allemand
de.kbd:pt:Alemão
de.kbd:es:Alemán
de.kbd:tr:Almanca
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
de.kbd:uk:Німецька
de.acc.kbd:en:German (accent keys)
de.acc.kbd:da:Tysk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
de.acc.kbd:de:Deutsch (mit Akzenten)
de.acc.kbd:fr:Allemand (avec accents)
de.acc.kbd:pt:Alemão (com acentos)
de.acc.kbd:es:Alemán (con acentos)
de.acc.kbd:uk:Німецька (accent keys)
de.noacc.kbd:en:German (no accent keys)
de.noacc.kbd:da:Tysk (ingen accenttaster)
de.noacc.kbd:de:Deutsch (ohne Akzente)
de.noacc.kbd:fr:Allemand (sans accents)
de.noacc.kbd:pt:Alemão (no accent keys)
de.noacc.kbd:es:Alemán (no accent keys)
de.noacc.kbd:uk:Німецька (no accent keys)
gr.kbd:en:Greek (104 keys)
gr.kbd:da:Græsk (104 taster)
gr.kbd:fr:Grec (104 touches)
gr.kbd:el:Ελληνικό (104 πλήκτρων)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
gr.elot.acc.kbd:en:Greek ELOT
gr.elot.acc.kbd:da:Græsk ELOT
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
gr.elot.acc.kbd:de:Grieschisch ELOT
gr.elot.acc.kbd:fr:Grec ELOT
gr.elot.acc.kbd:el:Ελληνικό ΕΛΟΤ
gr.101.acc.kbd:en:Greek (101 keys)
gr.101.acc.kbd:da:Græsk (101 taster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
gr.101.acc.kbd:de:Grieschisch (101 Tasten)
gr.101.acc.kbd:fr:Grec (101 touches)
gr.101.acc.kbd:el:Ελληνικό (101 πλήκτρων)
il.kbd:en:Hebrew
il.kbd:da:Hebraisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
il.kbd:de:Hebräisch
il.kbd:fr:Hébreu
il.kbd:he:תירבע
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
hr.kbd:en:Croatian
hr.kbd:da:Kroatisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
hr.kbd:de:Kroatisch
hr.kbd:fr:Croate
hr.kbd:es:Croata
hu.101.kbd:en:Hungarian (101 keys)
hu.101.kbd:da:Ungarsk (101 taster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
hu.101.kbd:de:Ungarisch (101 Tasten)
hu.101.kbd:fr:Hongrois (101 touches)
hu.101.kbd:es:Húngaro (101)
hu.102.kbd:en:Hungarian (102 keys)
hu.102.kbd:da:Ungarsk (102 taster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
hu.102.kbd:de:Ungarisch (102 Tasten)
hu.102.kbd:fr:Hongrois (102 touches)
hu.102.kbd:es:Húngaro (102)
is.kbd:en:Icelandic
is.kbd:da:Islandsk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
is.kbd:de:Isländisch
is.kbd:fr:Islandais
is.kbd:pt:Islandês
is.kbd:es:Islandés
is.acc.kbd:en:Icelandic (accent keys)
is.acc.kbd:da:Islandsk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
is.acc.kbd:de:Isländisch (mit Akzenten)
is.acc.kbd:fr:Islandais (avec accents)
is.acc.kbd:pt:Islandês (com acentos)
is.acc.kbd:es:Islandés (con acentos)
it.kbd:en:Italian
it.kbd:da:Italiensk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
it.kbd:de:Italienisch
it.kbd:fr:Italien
it.kbd:pt,es:Italiano
it.kbd:uk:Італійська
jp.kbd:en:Japanese 106
jp.kbd:da:Japansk 106
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
jp.kbd:de:Japanisch 106
jp.kbd:fr:Japonais 106
jp.kbd:pt:Japonês 106
jp.kbd:es:Japonés 106
jp.kbd:uk:Японська 106
jp.capsctrl.kbd:en:Japanese 106x
jp.capsctrl.kbd:da:Japansk 106x
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
jp.capsctrl.kbd:de:Japanisch 106x
jp.capsctrl.kbd:fr:Japonais 106x
jp.capsctrl.kbd:pt:Japonês 106x
jp.capsctrl.kbd:es:Japonés 106x
jp.capsctrl.kbd:uk:Японська 106x
kz.kst.kbd:en:Kazakh
kz.kst.kbd:da:Kasakhisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
kz.kst.kbd:de:Kasachisch
kz.kst.kbd:fr:Kazakh
kz.io.kbd:en:Kazakh (with IO)
kz.io.kbd:da:Kasakhisk (IO)
kz.io.kbd:de:Kasachisch (mit IO)
kz.io.kbd:fr:Kazakh (avec IO)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
latinamerican.kbd:en:Latin American
latinamerican.kbd:da:Latinamerikansk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
latinamerican.kbd:de:Latein Amerikanisch
latinamerican.kbd:fr:Amérique latine
latinamerican.kbd:pt,es:América Latina
latinamerican.acc.kbd:en:Latin American (accent keys)
latinamerican.acc.kbd:da:Latinamerikansk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
latinamerican.acc.kbd:de:Latein Amerikanisch (mit Akzenten)
latinamerican.acc.kbd:fr:Amérique latine (avec accents)
latinamerican.acc.kbd:pt,es:América Latina (com acentos)
lt.kbd:en:Lithuanian
lt.kbd:da:Litauisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
lt.kbd:de:Litauisch
lt.kbd:fr:Lithuanien
lt.kbd:es:Lituano
no.kbd:en:Norwegian
no.kbd:da:Norsk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
no.kbd:no:Norsk
no.kbd:de:Norwegisch
no.kbd:fr:Norvégien
no.kbd:pt:Norueguês
no.kbd:es:Noruego
no.dvorak.kbd:en:Norwegian dvorak
no.dvorak.kbd:da:Norsk dvorak
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
no.dvorak.kbd:no:Norsk dvorak
no.dvorak.kbd:de:Norwegisch dvorak
no.dvorak.kbd:fr:Norvégien dvorak
no.dvorak.kbd:pt:Norueguês dvorak
no.dvorak.kbd:es:Noruego Idvorak
pl.kbd:en:Polish (programmer's)
pl.kbd:da:Polsk (programmør)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
pl.kbd:de:Polnisch (für Programmierer)
pl.kbd:fr:Polonais (pour programmeurs)
pl.kbd:pl:Polska (programisty)
pl.kbd:pt:Polonês (para programadores)
pl.kbd:es:Polaco (para programadores)
pl.dvorak.kbd:en:Polish Dvorak
pl.dvorak.kbd:da:Polsk Dvorak
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
pl.dvorak.kbd:de:Polnisch Dvorak
pl.dvorak.kbd:fr:Polonais Dvorak
pl.dvorak.kbd:pl:Polska Dvorak
pl.dvorak.kbd:pt:Polonês Dvorak
pl.dvorak.kbd:es:Polaco Dvorak
pt.kbd:en:Portuguese
pt.kbd:da:Portugisisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
pt.kbd:de:Portugisisch
pt.kbd:fr:Portugais
pt.kbd:pt:Português
pt.kbd:es:Portugués
pt.acc.kbd:en:Portuguese (accent keys)
pt.acc.kbd:da:Portugisisk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
pt.acc.kbd:de:Portugisisch (mit Akzenten)
pt.acc.kbd:fr:Portugais (avec accents)
pt.acc.kbd:pt:Português (com acentos)
pt.acc.kbd:es:Portugués (con acentos)
ru.kbd:en:Russian
ru.kbd:da:Russisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ru.kbd:de:Russisch
ru.kbd:ru:Русский
ru.kbd:fr:Russe
ru.kbd:pt:Russo
ru.kbd:es:Ruso
ru.kbd:uk:Російська
ru.shift.kbd:en:Russian (shift)
ru.shift.kbd:da:Russisk (shift)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ru.shift.kbd:de:Russisch (shift)
ru.shift.kbd:ru:Русский (shift)
ru.shift.kbd:fr:Russe (shift)
ru.shift.kbd:pt:Russo (shift)
ru.shift.kbd:es:Ruso (shift)
ru.shift.kbd:uk:Російська (shift)
ru.win.kbd:en:Russian (winkeys)
ru.win.kbd:da:Russisk (win-taster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ru.win.kbd:de:Russisch (winkeys)
ru.win.kbd:ru:Русский (winkeys)
ru.win.kbd:fr:Russe (winkeys)
ru.win.kbd:pt:Russo (winkeys)
ru.win.kbd:es:Ruso (winkeys)
ru.win.kbd:uk:Російська (winkeys)
es.dvorak.kbd:en:Spanish Dvorak
es.dvorak.kbd:da:Spansk Dvorak
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
es.dvorak.kbd:de:Spanisch Dvorak
es.dvorak.kbd:fr:Espagnol Dvorak
es.dvorak.kbd:pt:Espanhol Dvorak
es.dvorak.kbd:es:Español Dvorak
es.kbd:en:Spanish
es.kbd:da:Spansk
es.kbd:de:Spanisch
es.kbd:fr:Espagnol
es.kbd:pt:Espanhol
es.kbd:es:Español
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
es.acc.kbd:en:Spanish (accent keys)
es.acc.kbd:da:Spansk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
es.acc.kbd:de:Spanisch (accent keys)
es.acc.kbd:fr:Espagnol (avec accents)
es.acc.kbd:pt:Espanhol (com acentos)
es.acc.kbd:es:Español (con acentos)
si.kbd:en:Slovenian
si.kbd:da:Slovensk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
si.kbd:de:Slovenisch
si.kbd:fr:Slovène
si.kbd:pt:Eslovênio
si.kbd:es:Esloveno
sk.kbd:en:Slovak
sk.kbd:da:Slovakisk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
sk.kbd:de:Slovakisch
sk.kbd:fr:Slovène
sk.kbd:es:Eslovaco
se.kbd:en:Swedish
se.kbd:da:Svensk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
se.kbd:de:Schwedisch
se.kbd:fr:Suédois
se.kbd:pt,es:Sueco
ch-fr.kbd:en:Swiss-French
ch-fr.kbd:da:Schweizerfransk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ch-fr.kbd:de:Schweiz-Französisch
ch-fr.kbd:fr:Suisse-Français
ch-fr.kbd:es:Francosuizo
ch-fr.acc.kbd:en:Swiss-French (accent keys)
ch-fr.acc.kbd:da:Schweizerfransk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ch-fr.acc.kbd:de:Schweiz-Französisch (mit Akzenten)
ch-fr.acc.kbd:fr:Suisse-Français (avec accents)
ch-fr.acc.kbd:es:Francosuizo (con acentos)
ch.kbd:en:Swiss-German
ch.kbd:da:Schweizertysk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ch.kbd:de:Schweiz-Deutsch
ch.kbd:fr:Suisse-Allemand
ch.kbd:pt:Suiço-Alemão
ch.kbd:es:Germanosuizo
ch.acc.kbd:en:Swiss-German (accent keys)
ch.acc.kbd:da:Schweizertysk (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ch.acc.kbd:de:Schweiz-Deutsch (mit Akzenten)
ch.acc.kbd:fr:Suisse-Allemand (avec accents)
ch.acc.kbd:pt:Suiço-Alemão (com acentos)
ch.acc.kbd:es:Germanosuizo (con acentos)
ch.macbook.acc.kbd:en:Swiss-German (MacBook/MacBook Pro) (accent keys)
ch.macbook.acc.kbd:da:Schweizertysk (MacBook/MacBook Pro) (accenttaster)
ch.macbook.acc.kbd:de:Schweiz-Deutsch (MacBook/MacBook Pro) (mit Akzenten)
ch.macbook.acc.kbd:fr:Suisse-Allemand (MacBook/MacBook Pro) (avec accents)
ch.macbook.acc.kbd:pt:Suiço-Alemão (MacBook/MacBook Pro) (com acentos)
ch.macbook.acc.kbd:es:Germanosuizo (MacBook/MacBook Pro) (con acentos)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
tr.kbd:en:Turkish (Q)
tr.kbd:da:Tyrkisk (Q)
tr.kbd:de:Türkisch (Q)
tr.kbd:fr:Turc (Q)
tr.kbd:uk:Турецька (Q)
tr.kbd:tr:Türkçe (Q)
tr.f.kbd:en:Turkish (F)
tr.f.kbd:da:Tyrkisk (F)
tr.f.kbd:de:Türkisch (F)
tr.f.kbd:fr:Turc (F)
tr.f.kbd:uk:Турецька (F)
tr.f.kbd:tr:Türkçe (F)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
uk.kbd:en:United Kingdom
uk.kbd:da:Storbritannien
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
uk.kbd:de:Vereinigtes Königreich
uk.kbd:fr:Royaume Uni
uk.kbd:pt:Reino Unido
uk.kbd:es:Británico
uk.capsctrl.kbd:en:United Kingdom (Caps Lock acts as Left Ctrl)
uk.capsctrl.kbd:da:Storbritannien (Caps Lock fungerer som venstre Ctrl)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
uk.capsctrl.kbd:de:Vereinigtes Königreich (Caps Lock als linke Strg)
#uk.capsctrl.kbd:fr:Royaume Uni (caps lock acts as Left Ctrl)
#uk.capsctrl.kbd:pt:Reino Unido (caps lock acts as Left Ctrl)
#uk.capsctrl.kbd:es:Británico (caps lock acts as Left Ctrl)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
uk.dvorak.kbd:en:United Kingdom Dvorak
uk.dvorak.kbd:da:Storbritannien Dvorak
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
uk.dvorak.kbd:de:Vereinigtes Königreich Dvorak
uk.dvorak.kbd:fr:Royaume Uni Dvorak
uk.dvorak.kbd:pt:Reino Unido Dvorak
uk.dvorak.kbd:es:Británico Dvorak
uk.macbook.kbd:en:United Kingdom (MacBook)
uk.macbook.kbd:da:Storbritannien (MacBook)
uk.macbook.kbd:de:Vereinigtes Königreich (MacBook)
uk.macbook.kbd:fr:Royaume Uni (MacBook)
uk.macbook.kbd:pt:Reino Unido (MacBook)
uk.macbook.kbd:es:Británico (MacBook)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.kbd:en:United States of America
us.kbd:da:USA
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.kbd:de:US-amerikanisch
us.kbd:fr:États Unis d'Amérique
us.kbd:pt:Estados Unidos da América
us.kbd:es:Estadounidense
us.acc.kbd:en:United States of America (accent keys)
us.acc.kbd:da:USA (accenttaster)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.acc.kbd:de:US-amerikanisch (mit Akzenten)
us.acc.kbd:fr:États Unis d'Amérique (avec accents)
us.acc.kbd:pt:Estados Unidos da América (com acentos)
us.acc.kbd:es:Estadounidense (con acentos)
us.dvorak.kbd:en:United States of America dvorak
us.dvorak.kbd:da:USA dvorak
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.dvorak.kbd:de:US-amerikanisch dvorak
us.dvorak.kbd:fr:États Unis d'Amérique dvorak
us.dvorak.kbd:pt:Estados Unidos da América dvorak
us.dvorak.kbd:es:Estadounidense dvorak
us.dvorakr.kbd:en:United States of America righthand dvorak
us.dvorakr.kbd:da:USA højrehåndet dvorak
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.dvorakr.kbd:de:US-amerikanisch dvorak rechte Hand
us.dvorakr.kbd:fr:États Unis d'Amérique dvorakr
us.dvorakr.kbd:pt:Estados Unidos da América dvorakr
us.dvorakr.kbd:es:Estadounidense dvorak diestro
us.dvorakl.kbd:en:United States of America lefthand dvorak
us.dvorakl.kbd:da:USA venstrehåndet dvorak
us.dvorakl.kbd:de:US-amerikanisch dvorak linke Hand
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.dvorakl.kbd:fr:États Unis d'Amérique dvorakl
us.dvorakl.kbd:pt:Estados Unidos da América dvorakl
us.dvorakl.kbd:es:Estadounidense dvorak zurdo
us.dvorakp.kbd:en:United States of America Programmer Dvorak
us.dvorakp.kbd:da:USA programmør Dvorak
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.dvorakp.kbd:de:US-amerikanisch (Dvorak für Programmierer)
us.dvorakp.kbd:fr:États Unis d'Amérique dvorakp
us.dvorakp.kbd:pt:Estados Unidos da América dvorakp
us.dvorakp.kbd:es:Estadounidense dvorakp
us.dvorakx.kbd:en:United States of America dvorakx
us.dvorakx.kbd:da:USA dvorakx
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.dvorakx.kbd:de:US-amerikanisch dvorakx
us.dvorakx.kbd:fr:États Unis d'Amérique dvorakx
us.dvorakx.kbd:pt:Estados Unidos da América dvorakx
us.dvorakx.kbd:es:Estadounidense dvorakx
us.emacs.kbd:en:United States of America Emacs optimized layout
us.emacs.kbd:da:USA Emacs-optimeret layout
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.emacs.kbd:de:US-amerikanisch für Emacs optimiert
us.emacs.kbd:fr:États Unis d'Amérique emacs
us.emacs.kbd:pt:Estados Unidos da América emacs
us.emacs.kbd:es:Estadounidense optimizado para Emacs
us.ctrl.kbd:en:United States of America (Caps Lock acts as Left Ctrl)
us.ctrl.kbd:da:USA (Caps Lock fungerer som venstre Ctrl)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.unix.kbd:en:United States of America Traditional Unix Workstation
us.unix.kbd:da:USA traditionel Unix-arbejdsstation
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
us.unix.kbd:de:US-amerikanisch traditionelles Unix Layout
us.unix.kbd:fr:États Unis d'Amérique unix
us.unix.kbd:pt:Estados Unidos da América unix
us.unix.kbd:es:Estadounidense Unix tradicional
us.macbook.kbd:en:United States of America (MacBook/MacBook Pro) ISO-8859-1
us.macbook.kbd:da:USA (MacBook/MacBook Pro) ISO-8859-1
us.macbook.kbd:de:US-amerikanisch (MacBook/MacBook Pro) ISO-8859-1
us.macbook.kbd:fr:États Unis d'Amérique (MacBook/MacBook Pro) ISO-8859-1
us.macbook.kbd:pt:Estados Unidos da América (MacBook/MacBook Pro) ISO-8859-1
us.macbook.kbd:es:Estadounidense (MacBook/MacBook Pro) ISO-8859-1
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ua.kbd:en:Ukrainian
ua.kbd:da:Ukrainsk
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ua.kbd:de:Ukrainisch
ua.kbd:fr:Ukrainien
ua.kbd:uk:Українська
ua.shift.alt.kbd:en:Ukrainian (with Russian) (shift)
ua.shift.alt.kbd:da:Ukrainsk (med russisk) (shift)
Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. Files were converted with a Perl script which I'll shortly commit to the tools directory. This script is a much enhanced version of the one provided by ray@ and is expected to support the full kbdmap(5) syntax. The naming convention used is: <2-letter country code>.<variant>.kbd Only if there are multiple layouts for different languages: <2-letter country code>-<2-letter language code>.<variant>.kbd In nearly all cases, the keyboards are country specific, only. Currently there is only one case where the language was added ("ch-fr.kbd" for the Swiss-French keyboard layout). I choose to write Unicode character codes as hex numbers. While this increases the diff to the SYSCONS keymap files for the trivial cases (conversion from ISO8859-1), it really helps to verify the more complex cases against a Unicode table (which is indexed by hex numbers). This commit does not cover all files that have been converted, since I need to sort out which ones to use, if there were several with different source encodings to choose from. Review and test of the keymap files is highly desirable before 10.1 is released. I'd also appreciate educated opinions regarding the optimum variant (to be made available as the default for each language). Since there are no NEWCONS keymaps in 10-STABLE, I plan to MFC after the minimum allowed delay of 3 days, to allow at least a few weeks to test and improve what will be in the next release. MFC after: 3 days
2014-08-17 19:54:21 +00:00
ua.shift.alt.kbd:de:Ukrainisch (mit Russisch) (shift)
ua.shift.alt.kbd:fr:Ukrainien (koi8-u avec koi8-r) (shift)
ua.shift.alt.kbd:uk:Українська (koi8-u з) koi8-r (shift)