KrisHunter / shellinabox

Automatically exported from code.google.com/p/shellinabox
Other
0 stars 0 forks source link

Add support for belgian keyboard #207

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Use a belgian keyboard
2. keys not working ")°", "-_", "$*]", ":/", "ù%´", "<>\"
3. keys partially working "^¨[", 

What is the expected output? What do you see instead?
The same character as is printed on the key.  Nothing.

What version of the product are you using? On what operating system?
2.14 (build from source)  on Debian amd64

Please provide any additional information below.
A number of keys on a belgian keyboard have 3 characters, the third one is 
obtained in combination with the "Alt Gr" key, acting as a "modifier" or 
"shift".  
If someone can give me some hints about how to change the js, I could try it 
myself.

Original issue reported on code.google.com by ghpi...@gmail.com on 16 Oct 2012 at 6:54

GoogleCodeExporter commented 9 years ago
Solution: patch for vt100.h to add the unrecognised keys for the "Belgian 
French" keyboard:

2933a2934,2941
>   // Belgian French keyboard conflicts
>   // : - < ) $
>   // : 58
>   // < 60
>   // $ 164
>   // ù 165
>   // ) 169
>   // - 173
2946c2954,2960
<     event.keyCode == 226;
---
>     event.keyCode == 226 ||
>     event.keyCode == 58 ||
>     event.keyCode == 60 ||
>     event.keyCode == 164 ||
>     event.keyCode == 165 ||
>     event.keyCode == 169 ||
>     event.keyCode == 173;

I made the change to the vt100.h file starting from the shellinabox-2.14.tar.gz 
source archive and built the binary.
However I had some issues in the deployment of shellinaboxd, so I switched to 
retrofitting the above changes in the ShellInABox.js file from version 2.14 and 
serving it with the --static-file option.

I can confirm that, with the above changes, it works fine with my Belgian 
French keyboard.

Michel

Original comment by mjacqu...@gmail.com on 10 Jan 2014 at 1:11