Hi,
At Thu, 17 Oct 2002 09:32:31 +0200 (MEST),
David Monniaux wrote:
> I also noticed that if XMODIFIERS="@im=kinput2", kinput2 still does not
> work if the application is not launched in a ja_JP.* locale (fr_FR.UTF-8
> does not work).
Please try ja_JP.UTF-8 locale.
The locale limitation is on
On Thu, 17 Oct 2002, David Monniaux wrote:
> I find that some of the limitations regarding XIM and Compose regrettable.
Yeah, it is.
> Some things I thing should change:
> * It should be allowed to use several XIM methods in the same application
> at the same time.
Although it may not be us
Hi,
At Thu, 17 Oct 2002 12:22:48 +0200 (MEST),
David Monniaux wrote:
> That's what I use. kword and the like are able to use kinput2 if they are
> launched in the ja_JP.UTF-8 locale but not in they are launched in
> fr_FR.UTF-8.
Though I have no experience nor knowledge on writing XIM servers,
I
On Thu, 17 Oct 2002, Tomohiro KUBOTA wrote:
> > I also noticed that if XMODIFIERS="@im=kinput2", kinput2 still does not
> > work if the application is not launched in a ja_JP.* locale (fr_FR.UTF-8
> > does not work).
> Please try ja_JP.UTF-8 locale.
That's what I use. kword and the like are able
In answer to Pablo:
I find that some of the limitations regarding XIM and Compose regrettable.
Let me take a concrete example: I know a teacher of Japanese as a foreign
language that wants to type texts consisting of a mixture of French and
Japanese.
It would be impossible for her to do this in
