Two unknown character dumped while toggle IM deactive.

[GoogleCodeExporter]

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

Original issue reported on code.google.com by MatLinuxer2 on 10 Feb 2011 at 2:06

[GoogleCodeExporter]

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.

Original comment by cxcxcxcx@gmail.com on 28 Mar 2011 at 7:32

[GoogleCodeExporter]

how to make imexample？

Original comment by nature...@gmail.com on 23 May 2011 at 8:43

[GoogleCodeExporter]

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

Original comment by sbbg...@gmail.com on 9 Aug 2011 at 11:44

[GoogleCodeExporter]

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!

Original comment by MatLinuxer2 on 6 Aug 2012 at 3:27