Summary: | In xooffice 1.1.2, there input twice some charactor when using scim-hangul | ||
---|---|---|---|
Product: | scim | Reporter: | Kitae Kim <neeum> |
Component: | IMEngine: Other | Assignee: | James Su <suzhe> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | krisna |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
URL: | http://pds.egloos.com/pds/1/200408/28/72/b0006872_19403126.jpg | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Kitae Kim
2004-08-28 03:45:26 UTC
Hi, What is xooffice? And please check if option "On The Spot" is turned on. You can find it in scim-setup -> FrontEnd -> X Window Regards James Su Hi, xoofice is Ximian-OpenOffice. In scim-setup, I check on-the-spot.(I am will away set to on-the-spot) I think that's some strange thing. In java, gtk, qt, kde, most work fine. Olny in Ximian-Open-Office, in file name fild, have problem, like upper screenshot image. There is problem using xooffice, editing and writting. and scim attached with on the spot. only file name filed got problem. So please try to turn off "On The Spot". Because some clients including OpenOffice do not support On The Spot very well. Thanks for your sugesstion. I know if I change on-the-spot turn off, I can input Korean correctly. But if then, all other progam and in openoffice main window editing use over the spot, that is tooooooo inconvenience for Korean, and using Hangul. As I always said I don't know about programing, but other XIM program like Nabi(Korean most favorite XIM) don't have same problem. So I think, scim can and I hope work well with OpenOffice. Thanks PS. All OpenOffice is same.(just test on gentoo ppc and x86) Kitae Hi, It's indeed a bug of OOo. Setting preedit caret position is buggy in OOo. Anyway I had committed a workaround into scim-hangul svn trunk. Could you please have a test? Thanks a lot, James. I didn't know svn so got something delay. (find what is svn, and make ebuild) I have test now, that most work but, one charactor have problem, when I type "가" that just only display "ㅏ", I can't test every Korean charactor but try as I can, other all fine. Only "가" have problem, "각" display correctly. Other program and openoffice main edit window work fine. I think this webpage code is UTF-8 so you can see that Korean charactor. http://pds.egloos.com/pds/1/200408/29/72/b0006872_5193496.jpg That page show that word. Thanks Can you tell me how to input these characters? In sbul-390 mode "가" is "kf". "ㅏ" is "f" "각" is "kfx" yes only have problem "kf" "가" Thanks I tested scim-hangul r67. It works but shows wrong caret position. Is it possible to send caret position in PreeditDrawCallback with SCIM's api? I agree that it is a problem of OOO's preedit caret implemetation, too. But if we can, we should not call PreeditCaretCallback. How do you think? Before r67, scim-hangul will set the correct preedit caret position when updating preedit string. But it will cause this issue. So I removed the preedit caret setting code in r67. Now the preedit caret will never be changed. The wrong caret position is set by OOo itself. (In reply to comment #10) > Before r67, scim-hangul will set the correct preedit caret position when > updating preedit string. But it will cause this issue. So I removed the preedit > caret setting code in r67. Now the preedit caret will never be changed. > > The wrong caret position is set by OOo itself. I mean OOo is to blame. Anyway, OOo does not manage caret callback currectly, so I suggest that scim-hangul does not call caret callback, but uses preedit draw callback with caret position data. Is it possible in SCIM api? Ok, I see. But it's impossible to set arbitary caret position with preedit draw callback. Though I can fix scim to set caret position to the end of preedit string in preedit draw callback, is it ok? (In reply to comment #12) > Ok, I see. But it's impossible to set arbitary caret position with preedit draw > callback. Though I can fix scim to set caret position to the end of preedit > string in preedit draw callback, is it ok? Yes, I think it will solve this problem :) Could you please try the lastest scim cvs head? It should have been fixed. (In reply to comment #14) > Could you please try the lastest scim cvs head? It should have been fixed. Ok, now it works fine. Thanks. Close this bug. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.