libindicator

Bug #564034
Comment #42

Comment 42 for bug 564034

Revision history for this message

YunQiang Su (wzssyqa) wrote on 2010-08-19: Re: [Bug 564034] Re: Panel no longer shows which input method is being used

#42

yes, it appears on indicator,now.
good job.

On Thu, Aug 19, 2010 at 12:27 AM, Karl Lattimer <email address hidden> wrote:
> I have uploaded my fixed and tested ibus package to the following ppa:
> https://launchpad.net/~karl-qdh/+archive/ppa
>
> The libindicator update is due either tonight or tomorrow, the
> libindicator update is required to show the icons.
>
> ZhengPeng Hou, YunQiang Su I hope you both can find the time to test
> this fix
>
> --
> 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 Ayatana Ubuntu Love Project: In Progress
> Status in Libindicator: Fix Released
> Status in “ibus” package in Ubuntu: In Progress
> 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/ayatana-ubuntu/+bug/564034/+subscribe
>

--
YunQiang Su

yes, it appears on indicator,now.
good job.

On Thu, Aug 19, 2010 at 12:27 AM, Karl Lattimer <karl@qdh.org.uk> wrote:
> I have uploaded my fixed and tested ibus package to the following ppa:
> https://launchpad.net/~karl-qdh/+archive/ppa
>
> The libindicator update is due either tonight or tomorrow, the
> libindicator update is required to show the icons.
>
> ZhengPeng Hou, YunQiang Su I hope you both can find the time to test
> this fix
>
> --
> 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 Ayatana Ubuntu Love Project: In Progress
> Status in Libindicator: Fix Released
> Status in “ibus” package in Ubuntu: In Progress
> 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/ayatana-ubuntu/+bug/564034/+subscribe
>

-- 
YunQiang Su