On 2014-08-29 18:53, William Hua wrote: > im-config was patched so that under Ubuntu, Fcitx would be prioritized > over IBus.
Actually that code in debian/rules is included upstream. It's there for a reason - Ubuntu Kylin - and if it's going to be dropped, some other solution for Ubuntu Kylin must be in place first. > This was fine before because Fcitx wasn't a seeded package > and installing Fcitx explicitly meant that you pretty much wanted it. > But if Fcitx is seeded, this means that patch effectively makes Fcitx > default, so we need to revert that behaviour. What would the point be with seeding Fcitx in distros where it's not supposed to be the default? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1363150 Title: [FFe] Fcitx input method integration in Unity Status in Indicator keyboard: New Status in Unity Control Center: New Status in Unity Settings Daemon: New Status in “fcitx” package in Ubuntu: New Status in “fcitx-qimpanel” package in Ubuntu: New Status in “im-config” package in Ubuntu: New Status in “indicator-keyboard” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Bug description: Fcitx is being included in main, but Unity lacks support for it in various ways: - The Text Entry panel in unity-control-center has no effect on Fcitx' engine list - Per-window source options in Text Entry panel don't affect Fcitx - Fcitx engines (specifically for keyboard layout) are not available under unity-greeter - Fcitx indicator isn't available under the lock screen, only indicator-keyboard - Keyboard layout switching shortcut behaviour provided by Unity and unity-settings-daemon doesn't change Fcitx' current IM - Fcitx indicator is missing some options that are normally provided by indicator-keyboard - Running indicator-keyboard and Fcitx concurrently is redundant as indicator-keyboard only works with Xkb layouts and IBus IMs Some of the changes we need: - Add support for Fcitx input sources to unity-settings-daemon, unity-control-center, indicator-keyboard - Customize the Fcitx indicator under Unity to show some menu options that are available in indicator-keyboard (already merged upstream) - Hide indicator-keyboard in the session when Fcitx' indicator is visible - Add D-Bus property to Fcitx API for the current IM, so that we can detect when the user changes the current IM in the Fcitx indicator, and update the current input source accordingly (already merged upstream) - Use indicator-keyboard icons for keyboard layouts in Fcitx and fcitx-qimpanel when running under Unity We have a PPA that includes most of the proposed changes. It is available at https://launchpad.net/~fcitx-team/+archive/ubuntu/fcitx- transition. It does not hide indicator-keyboard in the session yet, as having both indicators visible is helpful for testing purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1363150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
