Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

input-tools icon on the wingpanel(not keyboard) #4

Closed
elementaryBot opened this issue Apr 14, 2017 · 5 comments
Closed

input-tools icon on the wingpanel(not keyboard) #4

elementaryBot opened this issue Apr 14, 2017 · 5 comments

Comments

@elementaryBot
Copy link
Contributor

Has any plan to fix the input-tools icon on the wingpanel?
After delete the panel icons,it links to the devices input-keyboard svg.
http://itmages.com/image/view/4999659/8d7e6b55
http://itmages.com/image/view/4999670/b5b5ddfc
Input-tools is the most important character for CJK.
I hope elementary's designers can think about that.
http://itmages.com/image/view/4999697/35278b5b
The black design looks very calm.
Please add that child to the new design, don't miss him.
Thanks.

Launchpad Details: #LP1631726 xhhqzxg24 - 2016-10-09 11:02:12 +0000

@elementaryBot
Copy link
Contributor Author

I believe this is for ibus maybe? Probably the easiest short-term solution would be carrying a patch for ibus to have it use input-keyboard-symbolic.

I'm not sure how this differs from using the built-in method for keyboard layout switching. I would like some guidance from i18n team here about what modifications might need to be made to our keyboard indicator so that we don't need to rely on this third-party indicator

Launchpad Details: #LPC Daniel Fore - 2016-10-09 15:01:40 +0000

@elementaryBot
Copy link
Contributor Author

we hope to have a much better integration with input methods in the next release so this kind of things can be managed from our language indicator, and the settings panel. For now, support for this depends a lot on which input method you are using.

Launchpad Details: #LPC Santiago - 2016-10-09 16:07:48 +0000

@elementaryBot
Copy link
Contributor Author

Sorry I am so late.
Hello,Daniel,I'm a Chinese.
I want to tell you something about my input-tool,fcitx.
You can find it on launchpad and github.
https://launchpad.net/~fcitx-team
https://github.com/fcitx

I like using the fcitx-sogou and fcitx-rime.
Fcitx-sogou has a super arts community.==>>http://pinyin.sogou.com/skins/
If you have a mac,
you will be the happiest one on the word world.==>>http://pinyin.sogou.com/skins/mac.php
Someone said , landscaping is the first productivity.
Ubuntu kylin&sogou developed the fcitx-sogou for linux,
and made this to be Ubuntu kylin & DeepinOS's defaule input-tool.
Fcitx-sogou also support the bigest chinese hesaurus. ==>> http://pinyin.sogou.com/dict/
But only some parts have been opensource.==>>https://github.com/sogoupinyin
Fcitx-sogou's maintainer is the sogou official team.

Fcitx-rime is RIME on fcitx. ==>>http://rime.im/
RIME is a Chinese input method engine has highly customizable.
This guy is a professional input tool for the linguists & geeks.
Rime's maintainer lotem is working for the google input tools.
Ibus also has ibus-rime,but fcitx makes rime more quick and stable.
Fcitx-rime also can support the beautiful skin with kimpanel.
It's maintainer is the fcitx official team, and it's opensource.

Loki Chinese language default input-tool is fcitx add by ubuntu.
But gnome only use ibus,
you know ,elementaryOS is ubuntu+gnome ,so many things came to us.

The fcitx maintainer csslayer is a big fan of KDE&OPENSUSE,
and gnome don't pay attention to it,
that makes almost most CJK developers leave gnome to use KDE.

Last month , I saw a very sad thing.
https://code.launchpad.net/~elementary-os/elementaryos/os-patch-fcitx-xenial
By Cody Garver on 2016-09-08
No longer recommend fcitx-frontend-gtk3 as it breaks a lot Pantheon apps.

Fcitx has command fcitx-diagnose to check the problem,
when you want to know what happen with your fcitx,
you can use it to fix the bug.
My fcitx-diagnose shows GTK_IM_MODULE=xim after delet fcitx-frontend-gtk3.

Warning:
Using xim can sometimes cause problems including not being able to input,
no cursor following, word selection window issue, application freeze on input method restart.
For these xim related problems, Fcitx cannot provide any fix or support.
This is the same with any other input method framework,
so please use the GTK+ and Qt input method modules instead of xim whenever possible.
This is copy from fcitx's archwiki==>>https://wiki.archlinux.org/index.php/fcitx

After the Loki release,I have asked the fcitx maintainer csslayer.
https://groups.google.com/forum/?nomobile=true#!topic/fcitx/S5_wmg-jL94
He said this is not fcitx's power.

If someone want to use xim , only need to use the .profile set:
export GTK_IM_MODULE=xim
export QT_IM_MODULE=xim

I don't know why scratch-text-editor only support xim.
But I hope the scratch maintainers can take some time on another valac editor&notebooks.
Such as the writer==>> https://quassy.github.io/elementary-apps/Writer/
the notes up ==>> https://quassy.github.io/elementary-apps/Notes%20Up/
they all can use fcitx&ibus normal.

I have a lot of things want to tell you.
But my english is so bad.
Even you can't fix the scratch,you have done your best,
thanks,elementary,you're the best.

Santiago ,thanks for your kindness,
that input-keyboard design was made by Daniel.
http://icons101.com/icon/id_66344/setid_2061/Elementary_Icons_by_DanRabit/inputkeyboard
I only want to follow the black design, we can use the im-config.
That icon is the default input-keyboard icon on Freya.

Launchpad Details: #LPC xhhqzxg24 - 2016-10-10 17:55:43 +0000

@elementaryBot
Copy link
Contributor Author

sougoupinyin & fcitx-rime with kimpanel.
http://itmages.com/image/view/5008540/c9ef215c

Launchpad Details: #LPC xhhqzxg24 - 2016-10-11 08:48:35 +0000

@danirabbit
Copy link
Member

Closing since these screenshots don't look anything like the keyboard indicator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants