Marc-Andre,
Thanks for the comment.
I am going to try to explain it to the best of my knowledge. Please
bear with me that I don't have deep knowledge of keyboards or
programming for that matter. Also I have no idea for what goes on in
Chinese and Korean keyboards/IME.
> we need to pass an IME file along with a different keyboard type I
> believe.
>From my experience from trying to make the "\|" keycap on JIS Keyboard
work currently in FreeRDP, I don't think you need to pass IME file. You
just need to make sure that xfreerdp wil pass the correct keyboard
layout and the scancodes.
FYI, you can use IME on a US keyboards. Lots of my Japanese-writing
colleagues uses US Keyboards to input Japanese. They don't have any
issues using freerdp since their keyboard layout and scancodes are
correctly sent to the RDP server.
> 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?
We have 2 ways to input Japanese using IME.
Romaji input:
I believe this is the method used by most users.
1. The user will turn IME on by sending control sequence.
# When we want to type in 2-byte chars (ie Japanese), we turn IME
# on. IME can be toggled on/off by pressing sequence of control
# keys, ie, for US keyboard, it's "Alt" key and "`" key at the
# same time. JIS Keyboards have single key for this feature (as
# highlighted as scancode 29 in (*1))
(*1) http://www.win.tue.nl/~aeb/linux/kbd/jp106.jpg
2. The user will type in words and phrases phonetically using
alphabet (a,b,c...) keys.
# In this method, the Hiragana imprint (mostly) on right bottom on
# the keycap (*1) is ignored.
3. The user will hit "space" key to send them to IME and IME will
suggest kana/hiragana/kanji/2-byte_char combo.
4. The user will select and accept it by pressing the "enter" key.
The user may continue to type Japanese or toggle IME off.
Kana input:
The Kana input use is very rare, in all my 10+ yrs in the IT
business, I have never seem anyone use this method. I've never used
it myself.
The only difference to Romaji input is in step 2. where users will
type in words looking at the hiragana chars imprinted in the right
bottom part of the keycaps (*1) instead of phonetically.
> 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.
As stated above, for romaji input, alphabet (a,b,c,...) will be used to
type in words and phrases phonetically and they are replaced by
kana/hiranaga/kanji/2-byte char combo with IME. Same goes for kana
input expect hiranaga keys are used.
> Feel free to correct me on my ignorance, that's the main reason why we don't
> support those properly
I hope this helps a bit. Please let me know if I am being unclear
Regards,
Seiji T.
On Fri, Mar 23, 2012 at 5:40 AM, Marc-Andre 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
