[PATCH RFC] Add language and text-direction to text protocol

Jan Arne Petersen jpetersen at openismus.com
Fri Feb 1 00:00:49 PST 2013


On 31.01.2013 23:49, Weng Xuetian wrote:
> On Thursday 31 January 2013 20:50:00,Jan Arne Petersen :
>> Currently the context is state-less but even when we add state there, in
>> Qt, for example, there is currently just one input context per
>> application not one per widget.
> Not the per-widget case, but if you see the implementation of XIM in Qt 4.8, 
> it implements per window input context. And I also take the same approach for 
> fcitx, in both Qt4 and Qt5 version, and really see the benefit. Here is a use 
> case.
>
> One people use instant message with two different people, one you want to use 
> Chinese, and the other you want to use German. Here comes some knowledge that 
> know by only user, not the application. So, it is possible to let input method 
> to use Chinese in that window, and German in another window.
>
> Though there is only one QInputContext / QPlatformInputContext , but you can 
> also expose it as "multi" input context to the input method server.
> 
> What input context should be ?
> IMHO, input context should be the smallest element that will have different 
> property in application, 1 context? or 2 context? It should be decided by 
> application, not by changing the property of input context every time.

We should specify that somehow in the text protocol documentation, so
that the toolkit implementations will take that into account.

-- 
Jan Arne Petersen
Openismus GmbH
http://www.openismus.com


More information about the wayland-devel mailing list