Re: I18n and xim

[Nicola Pero]

Hi,

sorry for answering late.

Yes - there are quite a lot of issues with text management in gnustep. :-)


>    My plan is first to implement a compose/dead keys (i.e. only for 
> european languages) patch 

Yes - european languages first :-) because they're easier

My suggestion is to have a look into 

NSInputManager / NSInputServer

in the MacOS-X documentation - because there is were the input managing is
supposed to be done according to their documentation.

MacOS-X uses a remote InputServer - we should think whether we want to
have that / whether it can be fit in our environment or not.

The questions we want to ask ourselves are probably - 

 * what are the advantages of having a remote input server 

 * what are the disadvantages of having a remote input server

 * how would that fit in our environment

I've not yet thought about these issues, so I don't have answers ready.


> Then for asian languages, it means far more changes because of the need 
> to inform XIM about text input widgets and so a good coordination.

Hm - I'm quite sure MacOS-X supports them through the NSInputServer - I'm
not sure how much that will adapt to X


>    And now the questions :

> - Is there anybody working on this right now ?

not really - but I'm probably the one having done more work on keyboard
input up to now

I might take long to answer because I've my hands in too many things :-)
please be patient and don't let you down just because I'm sometime slow in
answering.


> - To whom must I send the patches, or just on the list ? 

Please send patches to the list.

If you start working on it and want to discuss or are unsure about
something please send mails to the list as well.


> - Do I need to do a copyright assignment to the FSF ?

Yes