[cotvnc-devel] [ cotvnc-Bugs-1049564 ] German and Swiss-German Keyboards do not work.
Project superseded by http://chicken.sourceforge.net/
Brought to you by:
smeger
From: SourceForge.net <no...@so...> - 2004-11-19 12:55:13
|
Bugs item #1049564, was opened at 2004-10-18 13:43 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507159&aid=1049564&group_id=64347 Category: None Group: v2.0 Status: Open Resolution: None Priority: 5 Submitted By: Sven Nueesch (nueesch) Assigned to: Nobody/Anonymous (nobody) Summary: German and Swiss-German Keyboards do not work. Initial Comment: Most of the special keys !"§$%&/()=?`*'-:; do not work or are in the wrong place on a German or on a Swiss-German keyboard. Server: OSXvnc 1.4 Chicken of the VNC 2.0b2 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-11-19 04:55 Message: Logged In: NO PS: If I switch to the US keymap on my Powerbook the '[]' appear in the session. So it really seems to be a problem on the Mac side. Ingo. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-11-19 04:16 Message: Logged In: NO > This is largely a limitation of the OSXvnc 1.4 server > and not generally a CotVNC problem (AFAIK). Unfortunately it really seems to be a problem of CotVNC as I experience the same problems (unable to use e.g. '[]') with the RealVNC-Server on a Intel-Linux machine. :-( VNCThing at least can produce the '[]' but misses some other characters on the keybord. But its high processor load makes it almost unuseable. Anyway, I prefer CotVNC because of its nice UI and stability. Ingo Keck (ingo.keck at biologie.uni-regensburg.de) ---------------------------------------------------------------------- Comment By: Jonathan Gillaspie (jonathanosx) Date: 2004-10-20 07:57 Message: Logged In: YES user_id=631278 We have access to AppleRemoteDesktop 2.0 (Client and Admin) and we saw the same problem with the foreign keyboard settings we tried. I can't say specifically what you tested but since the ARD client is using VNC for the remote control protocol I would be surprised to see it behave differently. It's possible that the older ARD, that wasn't based on VNC, worked better with international keyboards but in our testing ARD 2 did not. -- Jonathan ---------------------------------------------------------------------- Comment By: Sven Nueesch (nueesch) Date: 2004-10-19 23:44 Message: Logged In: YES user_id=921320 Thanks a lot for the suggestion. -keyboardloading 0 helps a bit The following characters work now: !"$%*&()-_ What doesn´t not work is: /=#; Plus all characters produced with option as: []{}|This seems to be a real problem for all those using a foreign keyboard. Using a Terminal on a remote computer by vnc is impossible (happily ssh -l user ip-address can help there). I tested the hint on MacOSHint using the freely available Apple Remote Desktop Client as a VNC server, which unfortunately has the same limitations. How does Apple do it in Apple Remote Desktop Admin then??? By the way for all foreign users: No need to test them all: VNC Dimension, Share my Desktop, VNCThing and combinations thereof have all the same problem. Only Timbuktu and Apple Remote Desktop Admin which are very expensive seem to have a solution. ---------------------------------------------------------------------- Comment By: Jonathan Gillaspie (jonathanosx) Date: 2004-10-19 07:48 Message: Logged In: YES user_id=631278 This is largely a limitation of the OSXvnc 1.4 server and not generally a CotVNC problem (AFAIK). To summarize the difficulty of the situation -- Mac OS X can't "generate a character" it can only hit a key. The keyboard facilities within Mac OS X also don't offer a simple way to determine what keystroke produces a particular key (they only list it the other way around, and the reverse mapping is non-trivial). Anyhow for OSXvnc 1.4 we recommend launching the server with this argument -keyboardloading 0 That may help somewhat but it still isn't a complete solution. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507159&aid=1049564&group_id=64347 |