What steps will reproduce the problem? 1. download fbterm-1.7.0.tar.gz and build as usual ( also make imexample ) 2. cd top_srcdir of fbterm ( into fbterm-1.7/ ) 3. ./src/fbterm -i ./im/imexample

What is the expected output? What do you see instead?

Two unknown characters ( seems to be [0x9d,0xb9] ) will be dumped to tty.

Please use labels and text to provide additional information.

http://code.google.com/p/ucimf/issues/detail?id=77 http://code.google.com/p/ucimf/issues/detail?id=79

I'm suffering from this problem with 1.7, too. I tried many input methods, ucimf, ibus-fbterm and yong. All are suffering from this problem.

how to make imexample？

So am I. How I wish this could be resolved. Any idea about what could be wrong?

Hi all, I just received a great patch sent from Ruikai Liu:

=================================================================== --- fbterm-1.7/src/improxy.cpp 2010-10-06 00:23:08.000000000 -0400 +++ fbterm-1.6/src/improxy.cpp 2009-11-13 20:00:00.000000000 -0500 @@ -127,8 +121,8 @@ { if (!mConnected) return;

• TtyInput::instance()->setRawMode(mRawInput && !mActive); mActive ^= true;
• TtyInput::instance()->setRawMode(mRawInput && mActive);

Though these two should have the same meaning, it seems that mActive is also used in the function setRawMode.

I have try it, and this did work!! Good Job!