[Uim] uim 1.3.0-alpha released

Etsushi Kato ek.kato at gmail.com
Tue Dec 5 12:22:29 EET 2006

On 12/5/06, Etsushi Kato <ek.kato at gmail.com> wrote:
> On 12/5/06, YAMAMOTO Kengo / YamaKen <yamaken at bp.iij4u.or.jp> wrote:
> > I've noticed that you've added these new keysyms to 1.3.0. But
> > I'm not confident about their necessity and properness of the
> > input model. Do you really need these keys at now? If not, I
> > prefer keeping them unsupported for now.
> Off course these keys are normally uses as modifers, but I recently

Oops typo.  I mean,

> Off course these keys are normally used as modifers, but I recently

> noticed that some IMs uses Caps_Lock as as normal keysym to change
> input mode (in Chinese IM).  This is the reason I added these keysyms.
>  I think it is better than nothing.
> > These 'lock' keys involves the 'locked' state information, and
> > especially the Caps_Lock's one is normally managed by client
> > side. And as far as I know, it should be handled with Caps_Lock
> > MODIFIER information in addition to its own press/release
> > information, to make sense by application (uim) side.
> >
> > But since I'm not confident about whether adding the modifiers
> > to enum UKeyModifier is sufficient to model inputs involving the
> > keys, I think that it requires a careful investigations,
> > considerations and discussions.

For the modifier state issue in uim, let's discuss after 1.3.0.

Etsushi Kato
ek.kato at gmail.com

More information about the uim mailing list