Searched hist:270114 (Results 1 - 5 of 5) sorted by last modified time
| /freebsd-11-stable/share/vt/keymaps/ | ||
| H A D | jp.kbd | diff 270114 Sun Aug 17 18:00:54 MDT 2014 se 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 |
| H A D | jp.capsctrl.kbd | diff 270114 Sun Aug 17 18:00:54 MDT 2014 se 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 |
| H A D | INDEX.keymaps | 270114 Sun Aug 17 18:00:54 MDT 2014 se 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 |
| H A D | Makefile | diff 270114 Sun Aug 17 18:00:54 MDT 2014 se 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 |
| H A D | us.kbd | diff 270114 Sun Aug 17 18:00:54 MDT 2014 se 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 |
Completed in 147 milliseconds