On Monday 21 March 2011 18:26, Harald Becker wrote: > Bump for comments! I got really stuck at this question. > > Hi all! > > Due to the fact that my notebook keyboard definition doesn't fit my > needs, I have written a new keyboard definition table from scratch > (boring work). After testing that new definition with the upstream > loadkeys command I created a binary keyboard table for Busybox with > "loadkeys -b" ... and was really annoyed as I noted that all my function > key definitions are not loaded using Busybox loadkmap. > > Investigating this, I found that Busybox doesn't allow loading the > function key string and the diacritical tables. That functionality is > completely missing. Is there anything wrong with those or is this just > historical?
Most likely it is just historical. > Can we improve Busybox and add those functionalities? Attention: > Modifications at this point probably introduces an incompatibility to > current Busybox versions, as the format of the key table will change > (don't know if we can extend without format changes). That may need > conversion of all existing binary key tables AND will affect the > upstream keyboard packages loadkeys command (needs to adapt format > changes). I can do those changes and provide patches, but I didn't want > to go that way without asking, if those changes get accepted (due to > possible table incompatibilities). The best way would be to evolve tovards using data formats and command-line options which are compatible with relevant standard tools. If this makes new busybox incompatible with old versions, so be it. -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
