Currently, the default configuration is to start Xvnc with a simulated Swedish physical keyboard, ie xserver_args contains "-KeyboardMap=sv". Also, /appservergroups/rdp/default/keyboard_layout is set to "sv". The reasoning behind this is that Swedish can be considered a superset of the US map. Thus, we can have a solution that works with most keyboard symbols and applications in the default configuration for both Nordic countries as well as the US/UK.
However, as pointed out by http://lists.cendio.se/pipermail/thinlinc-technical/2013-January/000216.html, this isn't entirely true: If you have different keybindings for "X-symbol" and "X-Shift-symbol", you will have problems if the symbol can only be found in a shifted column in the keyboard map. This is the case with semicolon in the swedish layout.
One solution could be to try to identify that cases where this is a problem, and add those symbols in unshifted columns as well. But that could be difficult or even impossible, and the keyboard layout would no longer match the keyboard layout of a physical workstation.
Another solution is to use US keyboard maps by default instead. In that case, we would need to check what problems we will have with Swedish keyboards. In theory, well-behaved applications should work.
Bug 3074 changed the default Xvnc layout to "us". appservergroups.hconf updated in r27079.
Changing the layout rdesktop has more severe consequences than for Xvnc, so a discussion is warranted.
Options for rdesktop and the problems it causes:
a) Default layout: en-us
Non-ascii characters will not work. This includes common Swedish characters like åäö, the german ü, etc.
b) Default layout: sv
Same problem as for X11; pressing things like Alt+; results in Alt+Shift+; on the WTS.
Swedish characters work, but characters from other layouts, like german, are still broken.
c) Default layout: de
Same issues as for 'se' really, just a different set of characters that are affected.
d) Default layout: none
rdesktop will in this mode look at the locale and make a guess. As long as people use their local language and not English, then this has a high probability of guessing the correct layout.
We've decided on d). Need to check the documentation as well to make sure that behaviour is documented.
Fixed in r27098.