At 11:45 AM 4/3/00 +0200, Henrik Berg wrote:
>> This is my _draft proposition_ how to get unicode chars from unix
>> keyboard.
>> This patch is for europe latin based languages, greek, cyrillic.
>> I'm not sure it's working fine and working with all europe languages.
>> Any comments, corrections are accepted.
>
>I looked at the patch and it looks like a good start. Basicly the same I
>did in Win32, except I could use Win32 system keyboard translation. I still
>hope that we can find a compleate X11key-->Unicode translation. Some one
>must have done it before.
>
>One thing about the keybindings. If you could include in the patch a
>default for 'insertData'. I can't find any good reason to have the table
>filled with:
>
> {0x455, /* */ { "insertData", "", "", "" }},
> {0x456, /* I UKR/BYEL */ { "insertData", "", "", "" }},
> {0x457, /* YI UKR */ { "insertData", "", "", "" }},
> {0x458, /* */ { "insertData", "", "", "" }},
> {0x459, /* */ { "insertData", "", "", "" }},
>
>just to add the character to the document. This should be the deafult
>behavior. Maybe we need to add undefined characters to the list to avoid
>them to be inserted.
Vadim and Henrik,
This sounds like a good suggestion. Anytime the keybinding lookup fails for
an *unmodified* character, I like the idea of defaulting to the insertData
edit method.
Does anyone foresee any potential problems with this?
Paul
