One key stroke --> two code-points

Hi, I am working on Khmer localization (KhmerOS project). In Khmer, some of the basic vowels (which we include in the keyboard) require two code-points, so one keystroke must generate two code points. It used to be that we could do the conversion in KBX by generating a fictious code-point (P

Re: One key stroke --> two code-points

O/H Javier SOLA έγραψε: Hi, I am working on Khmer localization (KhmerOS project). In Khmer, some of the basic vowels (which we include in the keyboard) require two code-points, so one keystroke must generate two code points. It used to be that we could do the conversion in KBX by generating

Re: One key stroke --> two code-points

Thanks Simos !! Actually, we have had these additions for a while in X11. We will do an issue for GTK+, and use the variable meanwhile. What file is it in GTK+? I have not been able to find it. Thanks, Javier Simos Xenitellis wrote O/H Javier SOLA έγραψε: Hi, I am working on Khmer locali

Re: One key stroke --> two code-points

O/H Javier SOLA έγραψε: Thanks Simos !! Actually, we have had these additions for a while in X11. Hi Javier, Checking at http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=tree;f=nls/en_US.UTF-8 does not show these lines at the end. It is possible that these compose sequences were added a

Re: One key stroke --> two code-points

Hi Simos, > Checking at > http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=tree;f=nls/en_US.UTF >-8 does not show these lines at the end. It is possible that these compose > sequences were added as a patch to the distribution package. yes indeed, this addition was made by Suse for their pac

Re: One key stroke --> two code-points

Thanks, Simos for your kind and time. Much appreciated to Javier for brought a good solution indeed. Lao input method is need a similar solution. Javier please post your solution (where and how to define a new table for Khmer) so I can define these code points for Lao. Thanks, Anousak The Lao t

Re: One key stroke --> two code-points

Thanks, Simos for your kind and time. Much appreciated to Javier for brought a good solution indeed. Lao input method is need a similar solution. Javier please post your solution (where and how to define a new table for Khmer) so I can define these code points for Lao. Thanks, Anousak T

Re: One key stroke --> two code-points

Just checking: so this problem does not affect languages using precomposed Unicode? Vietnamese users _should_ be using precomposed forms for our added and combined diacritics. But I wonder if we should be ready for the fact that they might not. I was using a keyboard layout for a while whic

Re: One key stroke --> two code-points

O/H Clytie Siddall έγραψε: Just checking: so this problem does not affect languages using precomposed Unicode? Vietnamese users _should_ be using precomposed forms for our added and combined diacritics. But I wonder if we should be ready for the fact that they might not. I was using a keyboar

Re: One key stroke --> two code-points

Thanks for your prompt and helpful reply, Simos. :) On 15/06/2008, at 12:55 AM, Simos Xenitellis wrote: O/H Clytie Siddall έγραψε: Just checking: so this problem does not affect languages using precomposed Unicode? Vietnamese users _should_ be using precomposed forms for our added and com

Re: One key stroke --> two code-points

On 6/15/08, Clytie Siddall <[EMAIL PROTECTED]> wrote: > > However, if there is a need for decomposed forms anyway, it is good know > about it. > > > > I don't think there's much of a need, but there are definitely still > decomposed layouts and old input versions around, and especially old fonts.