t seems everyone has this problem - apart from those who use in any case the U.S. 104 key keyboard.
It is hardwired into the source of xnest.
I am wondering how one can fool the program - such as creating a symlink to the keyboard we are using and naming it as if it were the U.S. keyboard.
I have also played around with the keyboard extensions option (-kb +kb) and it seems to ignore it.
With regard to the symlink I find it so difficult to understand how X organises and references the keyboard layouts I would be most grateful if anyone could develop this idea of providing a falsely named symlink.
That, together with the security problem - xnest has to run with the option -ac before you can use the nested server - are the only hold-ups I've met so far in using xnest.
At the moment I now run two servers: one on :0 and one on :1 - not the best solution but better than nothing.
t seems everyone has this problem - apart from those who use in any case the U.S. 104 key keyboard.
It is hardwired into the source of xnest.
I am wondering how one can fool the program - such as creating a symlink to the keyboard we are using and naming it as if it were the U.S. keyboard.
I have also played around with the keyboard extensions option (-kb +kb) and it seems to ignore it.
With regard to the symlink I find it so difficult to understand how X organises and references the keyboard layouts I would be most grateful if anyone could develop this idea of providing a falsely named symlink.
That, together with the security problem - xnest has to run with the option -ac before you can use the nested server - are the only hold-ups I've met so far in using xnest.
At the moment I now run two servers: one on :0 and one on :1 - not the best solution but better than nothing.