[Bug 83697] Re: Scim doesn't work in openoffice

2008-02-13 Thread Rolf Leggewie
** Changed in: scim (Ubuntu) Status: Incomplete = Fix Released -- Scim doesn't work in openoffice https://bugs.launchpad.net/bugs/83697 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

[Bug 83697] Re: Scim doesn't work in openoffice

2008-02-12 Thread Jan Ask
Hi Rolf, Almost forgot about this bug - Thanks for reminding me. I am using Scim in Openoffice in both Hardy and Gutsy, so I guess we can close this one. -- Scim doesn't work in openoffice https://bugs.launchpad.net/bugs/83697 You received this bug notification because you are a member of

[Bug 83697] Re: Scim doesn't work in openoffice

2008-02-12 Thread Rolf Leggewie
still a problem in gutsy or hardy? ** Changed in: scim (Ubuntu) Assignee: (unassigned) = Rolf Leggewie (r0lf) Status: New = Incomplete -- Scim doesn't work in openoffice https://bugs.launchpad.net/bugs/83697 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 83697] Re: Scim doesn't work in openoffice

2007-05-17 Thread Ming Hua
Does this bug still exist in the final feisty release? Also you may want to have a look at bug #107391, which also talks about using Japanese input method with scim. -- Scim doesn't work in openoffice https://bugs.launchpad.net/bugs/83697 You received this bug notification because you are a

Re: [Bug 83697] Re: Scim doesn't work in openoffice

2007-05-17 Thread Jan Ask
Thanks for getting back to me. I think this bug might be related to 34282. SCIM has been behaving strangely during the Feisty Release cycle - and still does in final :) I suggest marking it as a duplicate. -- Scim doesn't work in openoffice https://bugs.launchpad.net/bugs/83697 You received

[Bug 83697] Re: Scim doesn't work in openoffice

2007-05-17 Thread Ming Hua
Thanks for the reply, Jan. Since it still exists in final feisty, I'll leave this bug alone. I am very reluctant to label it as a duplicate to bug #34282, because to be honest, I don't exactly understand what the problem reported in #34282 is -- there are just so many issues mentioned there, --