Ok, just read more of the original info that was given, here's what I think:
scancodes are normally hardware-specific, and RDP uses scancodes over the network. Those scancodes are indeed always the same for the single keyboard type which we're currently using (the generic IBM keyboard type). Since CJK languages likely require that the keyboard type is changed (different keyboard type id) my guess is that scancodes are no longer the same for this different keyboard type. This means we would likely have to write a different scancode map for the Japanese keyboard type, to be used instead of the current one when a CJK language is in use. On Thu, Mar 22, 2012 at 4:40 PM, Marc-André Moreau < marcandre.mor...@gmail.com> wrote: > I have never tried making any of the CJK languages work due to lack of > knowledge regarding those. There is indeed significant differences in the > way those need to be handled, we need to pass an IME file along with a > different keyboard type I believe. > > If you have general information on how those keyboards work, it would > help. If I understood correctly words are written phonetically and the IME > would suggest a possible kanji for it, which you can accept with a special > key? > > I honestly don't know that much about Japanese and CJK input methods, I > guess that for Japanese hiraganas and katakanas could be used for typing in > words phonetically and then replace them with a kanji if necessary. > > Feel free to correct me on my ignorance, that's the main reason why we > don't support those properly > > Cheers, > - Marc-Andre > > > On Thu, Mar 22, 2012 at 4:28 PM, Mads Kiilerich <m...@kiilerich.com>wrote: > >> n 03/21/2012 07:01 AM, Seiji T wrote: >> > Dear all, >> > >> > I am trying to get 109 Japanese Keyboard (*1) to work with freerdp >> without >> > success. >> >> I guess a part of the real could be that the FreeRDP settings for >> kbd_type and kbd_subtype and kbd_fn_keys always are 0 when xfreerdp >> sends Client Core Data in gcc_write_client_core_data . >> >> That is according to http://msdn.microsoft.com/en-us/library/cc240510 >> not valid, and for japanese keyboards you might have to use keyboardType >> 7. That could in principle also change the rdp scan codes completely. >> >> I don't know if correct values for these settings can be determined from >> X (or windows) information somehow. >> >> If mstsc from windows works correctly then you could try to dump and >> analyze what it sends so we know how we could make it work. >> >> /Mads >> >> >> ------------------------------------------------------------------------------ >> This SF email is sponsosred by: >> Try Windows Azure free for 90 days Click Here >> http://p.sf.net/sfu/sfd2d-msazure >> _______________________________________________ >> Freerdp-devel mailing list >> Freerdp-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freerdp-devel >> > > ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
