As far as I know, Unity get Korean strings correctly from only IBus at now.
In latest Unity, it works as client of IBus(as result of fix bug ##880876).
So Unity depends on IBus and as result, Unity can't support nabi(which use XIM).
For now there is no bug report about using nabi at Unity, but I test it and notice this problem.
One more thing, does my patch need freeze exception to ship in precise?
As far as I know, Unity get Korean strings correctly from only IBus at now.
In latest Unity, it works as client of IBus(as result of fix bug ##880876).
So Unity depends on IBus and as result, Unity can't support nabi(which use XIM).
For now there is no bug report about using nabi at Unity, but I test it and notice this problem.
One more thing, does my patch need freeze exception to ship in precise?