Bug 230543 - transfer locally translateable keys as characters
Summary: transfer locally translateable keys as characters
Status: RESOLVED UPSTREAM
Alias: None
Product: krdc
Classification: Applications
Component: RDP (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-13 09:51 UTC by Maciej Pilichowski
Modified: 2010-03-15 21:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2010-03-13 09:51:09 UTC
Version:            (using KDE 4.4.0)
Installed from:    SuSE RPMs

This might be relevant also to VNC, but since I am working with RDP I can only say about it.

It would be useful if KRDC could check if the key combination I am using it translateable to a character (locally), and if yes, send this character instead of key combination. The reason is, the key combination on the remote side could be ambiguous or even not recognized as a character.

My problem: I try to enter some Polish characters, when I press alt+o (for example) which locally produces "รณ", alt (*) + o is send to to windows remote machine and this produces "oo".

(*) probably: the key physically is labeled alt, in windows (remote) it is altgr, in linux (local) is meta

The only workaround I know for now is using windows on-screen virtual keyboard to enter non-US characters.
Comment 1 Urs Wolfer 2010-03-14 22:46:43 UTC
KRDC RDP support is based on rdesktop. Rdesktop decides how to transfer keys. So please report this issue upstream to rdeskop developers and post the report # here. Thank you.
Comment 2 Maciej Pilichowski 2010-03-15 21:32:39 UTC
Ok, done, the report is here:
https://sourceforge.net/tracker/?func=detail&aid=2970843&group_id=24366&atid=381350