[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: slovene keyboard without dead keys
From:       Shachar Shemesh <wine-devel () shemesh ! biz>
Date:       2003-04-29 7:16:46
[Download RAW message or body]

Dmitry Timoshkov wrote:

>"Shachar Shemesh" <wine-devel@shemesh.biz> wrote:
>
>  
>
>>>>Also important is an ability by the system to change keyboards. One such 
>>>>requirement is for BiDi text editing, where the algorithm includes, 
>>>>among other things, instances where it is necessary to change the 
>>>>current keyboard layout.
>>>>   
>>>>
>>>>        
>>>>
>>>I'm not sure XFree86 supports this feature. Without support from X we couldn't
>>>implement keyboard layout changes on application request.
>>>
>>>      
>>>
>>Can't you set the current group? How are you planning on implementing 
>>"INPUTLANGCHANGEREQUEST" otherwise?
>>    
>>
>
>Just reflect the change on the X notification event and inform the app about it.
>
That's just INPUTLANGCHANGE, not the REQUEST. Let's hope it doesn't 
matter. I don't think many applications use this message to actually 
forbit a keyboard switch.

>>We use it today for comparing the keyboards.
>>    
>>
>
>If you mean X11DRV_KEYBOARD_DetectLayout, then we don't.
>  
>
Ok. I'l shut up until I collect further info.

>I'm afraid we can't change anything in that path.
>  
>
Again. I'll do my homework and call in again.

>There is a patch in CX Office which supports UTF-8 encoded keyboard input
>(in the case of UTF-8 locale of X Input Method) and makes it possible to avoid
>conversion to current locale code page and back to unicode. If Alexandre considers
>it clean enough he will certainly merge it into WineHQ tree.
>  
>
An improvement, and no doubt.

>I'm not an expert on right-to-left layouts and can't comment on this. If you
>(or somebody else) feel to be a motivated enough to learn how it supposed to
>work under real Windows and implement this behaviour in Wine taking into account
>X peculiarities that would be great.
>  
>
We'll see how this problem resolves in X. It may just be that the X 
keyboard is going to have the keys pre-reveresed, and we can get away 
with simply defining a new keyboard and having is done with.

                Shachar



[prev in list] [next in list] [prev in thread] [next in thread]