Owen Taylor wrote:
> On Tue, 2003-08-05 at 08:55, Ivan Pascal wrote:
> > Now Turkish keyboard users just have to set XkbOption "caps:shift".
> > With that option Xlib doesn't use 'internal capitalization' but CapsLock
> > key acts as 'locking Shift' (but can be canceled by Shift key). It solves
> > the problem.
>
> I don't think that this is a particularly good way to handling things.
> Using caps:shiftproduces all sorts of strange behavior - for example,
> the number keys will give their shifted variants.
I risk to seem impolite but did you try this option before making such
assertion? If you tried you would notice that it is not true.
> The Turkish user might well wonder why everybody else gets a useful
> caps lock key, while they have this monstrosity.
Do you have real complains from Turkish users?
The solution I offered was tested by Deniz Akkus Kanca and Nilgц╪n Belma
Bugц╪ner (an author of 'tr' keymap). They didn't notice any monstrosity
and accepted this solution.
I want to assure you it works as expected. CapsLock affects alphabetic keys
only. XKB automaticaly recognizes what keys are 'letter' ones. Shift
key being pressed cancels CapsLock action. What is wrong?
> It should be possible in Xlib's code for handling
> lock == Caps_Lock to simply special case this; if the lower case
> key is 'i', then check to see whether the key in the second level
> is 'I' or 'Idotabove', and act accordingly.
Of course, you may add a 'specila case' kludge to Xlib. But the problem you
want to solve doesn't exist actually.
--
Ivan U. Pascal | e-mail: [EMAIL PROTECTED]
Administrator of | Tomsk State University
University Network | Tomsk, Russia
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
