On Sun, 16 Sep 2007 16:47:01 +0600, "Alexander E. Patrakov" <[EMAIL PROTECTED]> wrote: > Matthew Burgess wrote: > >> I think what is needed here is to look in /lib/kbd/consoletrans and pick > a suitable [charset]_to_uni.trans file. > > No, the character sets for converting the keymaps are built into the > "dumpkeys" program, and the full list is available in the "dumpkeys > --help" output.
Thanks, I realised that once I tried booting with that incorrect setting. >> "There is no pre-made UTF-8 Russian keyamp, therefore it has to be > produced by converting the existing KOI8-R character set as illustrated > below (available non-Unicode to Unicode character set mappings are > available in /lib/kbd/consoletrans):" >> > > No. Maybe: "There is no pre-made UTF-8 Russian keyamp, therefore it has > to be produced by converting the existing KOI8-R keymap as illustrated > below. Correct spelling for source character set names for the > LEGACY_CHARSET option are available in the dumpkeys --help output." > > Or maybe move the "Correct spelling..." sentence to the description of > the LEGACY_CHARSET option description. > > Basically, the reader has to know that the existing Russian keymap is > for KOI8-R users, and that the correct spelling of this character set > name for dumpkeys is "koi8-r". > > And BTW, the next version of kbd does have a UTF-8 Russian keymap (as > "ru"), so we may need another example. Thanks for the information, Alexander. Where are the newer version of kbd being maintained? I'll try and get around to making a patch along the lines of what you posted above. It might be wise to find an example of a non-UTF-8 keymap that is present in both kbd-1.12 and the latest upstream sources, so that it's one less thing to update when the new version is released. >> Similarly, for fonts, how do I determine which ones are UTF-8 capable > and what flags I need to pass to setfont, via the FONT variable, so that it > will display correctly? >> > > All *.psfu.gz fonts are supposed to be displayed correctly, because > every font has the screen font map in it that maps font positions to > Unicode So, in a UTF-8 environment, I don't need to supply a '-m' switch, correct? That seems to be what the following suggests, as well (running an unpatched 2.6.22.6 kernel here). > FONT="lat1-16 -m 8859-1" # Suboptimal - no Euro sign, and the -m > option was used only by the patched 2.6.16 kernel in LFS-6.2 (for dead > keys and composing) Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
