Hallo Yann! >> That would be the loadkeys command and the keyboard table format >> described in the keymaps(5) manual page. ... but that one is an ASCII >> source table that needs complex parsing. That parsing, including dynamic >> table handling, would require a lot of code and data space. I don't >> think that this really hit's the Busybox "keep it small" philosophy. > What about the following: > - busybox applet that loads binary tables as you suggest > - script in the busybox source that converts an ASCII table into its > binary equivalent
A script would be really simple ... loadkeys -b KEYBOARD_DEFINITION_NAME >BINARY_KEY_TABLE ... thats all (using loadkeys from kbd-1.15.2 package). ... but that needs extending. Currently the definition of strings and diacriticals are silently discarded and not included in the binary key table (as Busybox can't load those). >> The standard tool "loadkeys" has an option "-b" to create the the binary >> key tables required by Busybox. > [--SNIP--] >> The standard tools loadkeys "-b" option is especially designed to create >> binary key tables in the format required by Busybox (see loadkeys manual >> page). > Sorry, my loadkeys man page does not document '-b': > $ loadkeys --version > loadkeys: (console-tools) 0.2.3 Ohps ... I think there are differences between console-tools and kbd package ... or are there newer versions of console-tools that provide "-b" on "loadkeys" ? On older console-tools you need to do two steps. Load your ASCII keyboard table with usual loadkeys command and then use Busybox "dumpkmap" to write the binary key table: loadkeys KEYBOARD_DEFINITION_NAME busybox dumpkmap >BINARY_KEY_TABLE ... but that way you change your current keyboard table too (which may be unintentionally). -- Harald _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
