[Bug 230218] New: kbabel does not allow skim to input Chinese chars
https://bugzilla.novell.com/show_bug.cgi?id=230218 Summary: kbabel does not allow skim to input Chinese chars Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers@suse.de ReportedBy: gubotruth@gmail.com QAContact: qa@suse.de CC: zsu@novell.com openSUSE 10.2 x86_64, KDE environment, all packages from the DVD. With scim/skim ok in all other K apps, Kbabel does not allow skim to input Chinese chars in its msgstr field. With Eng keyboard on, everything's good. However, with a Chinese IM on, it seems that every time I press a key, an IMEnd signal is sent. For instance, with pinyin on, I press "wo" in order to form a char query, it strangely runs into this way(from shell): sending IMStart with 0 chars to 0x9fdce0 sending IMCompose to 0x9fdce0 with 1 chars, cpos=0, sellen=1, text=我 sending IMCompose to 0x9fdce0 with 1 chars, cpos=1, sellen=0, text=我 sending IMEnd with 0 chars to 0x9fdce0, text= sending IMStart with 0 chars to 0x9fdce0 sending IMCompose to 0x9fdce0 with 1 chars, cpos=0, sellen=1, text=哦 sending IMCompose to 0x9fdce0 with 1 chars, cpos=1, sellen=0, text=哦 sending IMEnd with 0 chars to 0x9fdce0, text= And there will be no char to be display in Kbabel. This bug has been there since SUSE 10.1, also existing in SLE 10 series. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230218 stbinner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #1 from stbinner@novell.com 2006-12-21 06:51 MST ------- dupe of 230217 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com