when send chat message with uncomplete character by press 'enter' key, it doesnt send last preedit string(= uncomplete character). this tarball contain ebuild, and patch (very simple, just 1 line changed ^.^) Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 13685 [details] ebuild. this is based on gaim-0.63-r1.ebuild
Created attachment 13686 [details, diff] and patch... very simple patch :)
*** Bug 23270 has been marked as a duplicate of this bug. ***
thanks for the patch but please don't open 3 equal bugs the next time (I already marked the other two as duplicates, so don't worry ;)
is this still an issue on gaim-0.64?
Actually I can't see any problem here. I emerged both gaim-0.64-r2 and gaim-0.63-r1, but nothing happened when I sent a message with an incompleted character (using XIM). It just doesn't send any message unless I complete the character. Moreover, after I patched gaim-0.64-r2 with the patch (the part of affected source is the same), when I sent an imcompleted character I got an error: ** (gaim:18123): WARNING **: Invalid change to preedit string, first=0 length=5 (orig length == 0) What is the exact problem with gaim-0.63 and the expected results with the patch?
exact problem is that gaim send only committed string exclude preedit string. (all XIM, gtk-im-modules). and I dont know about 0.64-r2's error. please explain how to regenerate that error.
Created attachment 14608 [details, diff] another patch do similar thing this patch make gaim process key_press_event after gtk_im_context_filter_key_press(). so the conflict key-binding may work bad, but I think this is better because imhangul and im-ja also works good. thanks to Botond Botyanszki from im-ja dev-list.
To reproduce the problem, apply your patch (gtk_im_context_reset) to gaim-0.64-r2 and run gaim, then input some string with your XIM (I used skkinput) and press return key _before_ you finish converting the string. btw, should I close this bug since you submitted bug #24657?
Hmm... is the problem you are having still a problem in 0.65 with his patch? If so I can probably switch it out for your patch w/o too much trouble...
close this bug is better. let's talk on bug #24657.
okay, let's move there.
