Comment 37 for bug 564034

Revision history for this message
ZhengPeng Hou (zhengpeng-hou) wrote : Re: [Bug 564034] Re: Panel no longer shows which input method is being used

For CJK end users, we're using ibus+ibus-pinyin/anthy/chewing, what I can
tell, the latest upload of ibus can't make it work with latest ibus-pinyin
in my ppa.
On Sun, Aug 15, 2010 at 9:37 PM, Karl Lattimer <email address hidden> wrote:

> This is possibly related to a packing problem which has occurred between
> 1.2.0 and 1.3.7 the packaging issue means the ibus-m17n package has been
> removed and the files it provides have not been replaced in any other
> package.
>
> In order to test this, please add another input method, i.e. ibus-latex
> which doesn't rely on the m17n package
>
>

> --
> Panel no longer shows which input method is being used
> https://bugs.launchpad.net/bugs/564034
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (617865).
>
> Status in Libindicator: Fix Released
> Status in “ibus” package in Ubuntu: Confirmed
> Status in “ibus” source package in Lucid: Won't Fix
>
> Bug description:
> Binary package hint: ibus
>
> In ibus 1.2.0.20091215-1ubuntu3 and 1.2.0.20091215-1ubuntu2, IBus was
> changed to use a custom status menu ("application indicator") instead of a
> notification area item.
>
> Application indicators currently do not allow bitmap icons. So in bug
> 528213, the new indicator was altered to use a generic keyboard icon instead
> of the icon representing the current input method whenever the latter is a
> bitmap -- which is most of the time.
>
> This makes it unreasonably difficult to tell what input method you are
> currently using. According to Emmet Hikory, this problem will affect anyone
> who uses IBus to type Chinese, Japanese, or Korean, who uses an input method
> that does not cover all the characters they use, but who does not use a
> dedicated keyboard with specific keys for changing input method.
>
> Because of the number of people this affects, I think this may deserve
> fixing for Ubuntu 10.04, even though we're past Final Freeze. As I
> understand it, fixing it would involve removing 05_appindicator.dpatch from
> the package.
>
> Problem occurs in: Ubuntu Lucid
> Does not occur in: Ubuntu 9.10
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/libindicator/+bug/564034/+subscribe
>