Summary: | app-i18n/imsettings-1.7.2 breaks app-i18n/ibus, app-i18n/fcitx, etc. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | augustin <gentoo-bugs-augustin> |
Component: | Current packages | Assignee: | CJK Team <cjk> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | gentoo-bugs-augustin, nikulinpi |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
augustin
2018-03-13 02:02:59 UTC
(In reply to augustin from comment #0) Terminology: Fcitx, IBus etc. are input method frameworks. Input methods are e.g. pinyin or hangul. > Even without running any of app-i18n/imsettings, the mere fact of installing > it, breaks the input system configurations of every users on the system. > The culprit is the included script that is run when starting any X11 session: > /etc/X11/xinit/xinitrc.d/90-xinput Better to somehow change app-i18n/imsettings to not affect every user... > 5) Gentoo should enforce this standard, by requiring/strongly suggesting > that input method packages depend on app-i18n/im-chooser which provides both > a GUI and a simple script interface for users to easily switch input methods > (without requiring to restart the x-session). Alternatively, a simple > eselect-like tool for users could do the job. Neither app-i18n/im-chooser nor eselect-like tool should be required. app-i18n/im-chooser is a GTK+ application... KDE provides KIMPanel which provides better integration with KDE and supports Fcitx, IBus and SCIM. I think that almost each user chooses one of Fcitx/IBus/SCIM/UIM and continuously uses only this chosen input method framework (until it breaks...). Personally I like ~/.xprofile. So we might think about how to improve life for users who have app-i18n/imsettings, but without forcing other users to install any new tool. I cannot find KIMPanel. Which package is it in? (In reply to augustin from comment #2) > I cannot find KIMPanel. Which package is it in? kde-plasma/plasma-desktop (since 5.6.0, previously kde-plasma/kdeplasma-addons) I do have kde-plasma/kdeplasma-addons-5.11.5 installed. I still don't see kimpanel. How to run it and how to use it to easily select a chosen input method framework? My overarching goals are that of usability and user-friendliness. Gentoo should not be synonymous to geeky/hard to install nor to use. On the contrary: I like portage/emerge a lot because of its clear coloured output, and the appropriate pointers it provides, leading even a newbie user to the proper place to learn more and the proper action to take. In 17 years of linux usage, I always found configuring chinese input a hurdle, which sometimes proved to be insurmountable. So, whatever solution is adopted, it should be judged according to the following principles (revised from above): 1) Installing and configuring input method frameworks should be easy. 2) It should work out of the box, inasmuch as possible. 3) Adding a new package should *add* value to the system by providing new functionality, not *subtract* value (by breaking a previously perfectly running system). 4) In case of a misconfiguration, there should be clearly identifiable logs that properly explain what is wrong, with a proper pointer to the solution, so that user can quickly and easily identify the problem and recover from it. My experience in installing and configuring chinese input frameworks have always failed any definition of usability: http://temp.lesenjeux.fr/website-usability-faktoren.png http://temp.lesenjeux.fr/Usability.jpg http://temp.lesenjeux.fr/venn_usability.png And by judging the amount of forum threads I came across that discuss the same frustrations I experienced, I think it is high time a Linux distribution came to make things easy and consistent. (In reply to augustin from comment #4) > I still don't see kimpanel. How to run it https://userbase.kde.org/Plasma#Widgets "Add Widgets" -> "Input Method Panel" (name can be translated) Can confirm |