Thread: TOHKBD Layouts
View Single Post
mced's Avatar
mced is offline mced
2015-07-11 , 15:15
Posts: 115 | Thanked: 185 times | Joined on Apr 2011 @ Spain
#18
About custom layouts, I'm wondering how does Maliit handle upper case modifier (CAPS+key) when we're dealing with "no-letters" (numbers, signs...)

You know, when it's about standard latin letters, Maliit knows the rule "capitals' codes are lower's codes - 32"; and there's some magic code that links, e.g., "å" with "Å" (I guess it will be the same with "Ç" and "Ñ"... or we're f***ed).

But if we change KeyboardLayout.qml to, let's say, Malkavian's SP/CAT/POR/FR suggestion, code for the second row would end in something like:

Code:
row2.append({name:"P",   sym:"_",   size: 1})
row2.append({name:"'",   sym:"+",   size: 1})
row2.append({name:"Right Ctrl", sym:"", size: 2})
Will be any chance to take advantage of these three options on every key (key, CAPS+key, SYM+key) and add a second sign?


P.S: Taking a look at desktop Linux layout config files, they seem to be more flexible and powerful. /usr/share/X11/xkb/symbols/es example:

Code:
key <AC10>  { [    ntilde, Ntilde,   asciitilde, dead_doubleacute ] };
key <AC11>  { [dead_acute, dead_diaeresis, braceleft,   braceleft ] };

key <BKSL>  { [  ccedilla,   Ccedilla,   braceright,   dead_breve ] };