Originally Posted by Estel

No problem sulu - I've fixed monoblocks in wiki article (+ some minor typos, discovered during doing so). By the way, I think it's not a bug in Mediawiki - it's a feature While using #, every new line is recognized as end of 'counting', so it does for 'shortcut' way of inserting monospace (separated by new lines, and prefixed by double space). Using <pre></pre> (and avoiding any new liners, <pre> insert new line on it's own!) fixes the problem.

Originally Posted by Estel

During our latest research on xkb, I got idea, on how it may be possible to direct copy our Maemo (manually modified, as in Wiki article "Hardware keyboard remapping") keymap into ED - if proper ED xkb folder is basically Maemo one, maybe overwriting ED's rx-51 by our modified one, via...

Code:

cp -f /usr/share/X11/xkb/symbols/nokia_vndr/rx-51/.debian/usr/share/X11/xkb/symbols/nokia_vndr/rx-51

... from within Maemo (as root, with ED partition/image mounted), would work?

And guess what, it *does*! So now, everyone can use own Maemo hardware keyboard mapping - even most fancy one - inside LXDE. Every special character, symbol or 'command' (for example, TAB) work flawlessly! Just remember, to set correct setxkbmap inside LXDE (via autostart script, or manually) - for example, my custom Maemo keymap, where I 'binded' dead_ogonek as 'blue arrow' + shift + a for pl keyboard, works with:

Code:

setxkbmap pl

only (so, basically, everything is as it should be - there is no problem, if someone want to bind special characters to 'generic' layout as well - everything just works like with Maemo hardware keyboard remapping).

I'll test external keyboard tomorrow, but I'm 100% sure, that everything we need to get exact same result as with extkbd in Maemo, is to do to /.debian/usr/share/X11/xkb exactly same thing, as extkbd does to /usr/share/X11/xkb.

Originally Posted by Estel

I'll talk with freemangordon about that, asking him to include Easy Debian support in extkbd.