- What is Scim Bridge
Scim-bridge is yet another IM client of SCIM.
The im-module of scim-bridge communicates with scim via socket.

I developed this mainly because some of properity softwares written in C++ 
somtimes cause confilictions with system shared libraries also written in C++.
This is what you call "C++ ABI problem", and SCIM is known to cause such a problem in some cases.

I think this will solve that problem.
Because SCIM and such a software become different processes when you use scim-bridge.

And scim-bridge can be used for the preferable input method in multilibs environments;
You can use 64bit scim server from 32bit binary apps, like acroread or 32bit firefox.


- How to use it
The server of scim-bridge, "scim-bridge-agent" will be invoked automatically when you use scim-bridge.
So just choose "scim-bridge" as your IM.

You can choose "scim-bridge" manually in some gtk applications.
For example, you can launch gedit and switch IM by right-clicking.

Or you can export "scim-bridge" as an environmental variable "GTK_IM_MODULE".
After that, every application you launch will choose scim-bridge as default IM.
(Btw, I won't persuade you to use this as the default IM. It's too unstable for daily use.)

Scim-bridge-agent will exit by itself when there is no client.
"--stay" option disables this feature.


- How to debug it
There are two enviromental variables to enable debug output.

"SCIM_BRIDGE_DEBUG_LEVEL" is to choose how verbose the output will be.
"0" is to disable debug output completely, and "9" is to make it the most verbose.

The debug message from the agent will be shown in the terminal when the debug flag isn't 0.
You can debug it by launching it from another terminal, with a option of "--verbose."

All the messages from the agent are shown in the stdout except error messages, which are shown in the syslog. 
So you should use "--standalone" option to prohibit the agent detaching from the console if you want to see them.