Xpra: Ticket #706: Input cjk text on forwarded window

This is not perhaps less a bug report than a seek for help. It may be possible to input cjk text on, for example, a browser window from the remote machine, but I could not quite get it to work.

The description on the wiki about input method was relatively scant. Here's what I tried: I enabled xim on both server and client via command line. I installed fcitx input method on server machine and run it there. I use im-switch to make fcitx the default input method. But when I tried to switch input method on a forwarded client web window, by doing the usual ctrl-space, nothing happened.

I also tried several other combinations: installing scim on the remote machine, and enable scim as input method on both remote and local machines. Or use im-switch to put scim as default input method and enable xim again on both server and client.

Perhaps there's a way to get it work. If so, a more detailed documentation on the wiki would help. I'm willing to help on wiki if I could get it to work!

On the other hand, this is not a blocker bug for me. I could always use a local window to write the text in complex scripts and then copy and paste the text to the remote window. That is somewhat a hassle, though.

Other than this, and the weird URL bug filed under my name, xpra is about perfect for me! It essentially enable me to run my thin-client over gigabit setup. I use it every single day, as my preferred setup! Many thanks for developers!



Mon, 06 Oct 2014 13:56:14 GMT - Antoine Martin: owner changed

I enabled xim on both server and client via command line


The command line only affects applications started with start-child. And it sets up a few input related environment variables.

But when I tried to switch input method on a forwarded client web window, by doing the usual ctrl-space, nothing happened.


It could well be the same problem as #661 which is fixed in trunk and will be in the next release. It's difficult to say. Please see reporting keyboard bugs for providing more information.

I also tried several other combinations: ... If so, a more detailed documentation on the wiki would help


I really do not understand how all these input methods fit together or how they are meant to be configured, as I do not need or use them. The input-method command line option was written based on bits of information gleaned all over the place, and reading source code. If you do find more information, feel free to submit it.

I could always use a local window to write the text in complex scripts and then copy and paste the text to the remote window


That sounds like a major hassle!


Mon, 27 Oct 2014 17:47:29 GMT - Antoine Martin:

Can I close this? If not, please provide more information.


Tue, 28 Oct 2014 09:43:39 GMT - Antoine Martin: status changed; resolution set

Closing. FYI: the "reporting keyboard bugs" has lots of details on how to gather debug information.


Sat, 23 Jan 2021 05:03:33 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/706