Ibus-table Feature Request: Improve pinyin input

[omgcao]

what do you think of this issue?:

kaio#76

I agree with @champignoom. These CJK ideographs may should be removed, because ordinary people may be unable to distinguish these characters. But I'm not sure if it's necessary for publishping practitioners etc. to hold them for academic or other purposes.

In my perspective, the Pinyin Mode of ibus-table Wubi is the most difficult-to-use feature, which is the main reason why I use Linux for four years while just use ibus-table for about three months. Engine(s) that only support one Pinyin pharse to one character may be outdated, I think it's a 30-year-old technology.

This disadvantages of the engine(s) are:

1. The rate of coincident code is extremely high.
2. It's unable to cut a phrase to get a specified character, which is a frequently used and common way for people to obtain an unfimilar or uncommon character.

For a instance, the Chinese word (phrase) "貔貅【pí xiū】" (Pixiu). I believe that a lot of native Chinese speakers may know its pronuciation so they can compose corresponding characters with Pinyin, but they may don't know how to write it for its complex strokes.

So we may natrually think that users may press Right Shift key to toggle to Pinyin Mode for help. Press right Shift key then type 'pi' for 貔 character ... Guess what? After looking up all results in 16 pages, we cannot find this character, because it doesn't exsists in the current code table. Meanwhile, we may find the 貅 ('xiu') character at page 4.

For reference, if one use fcitx5 or ibus-rime, he or she may not need to press any modifiers, just type 'pixiu', then the two characters 貔貅 may show as the first candidate at page 1.

In addition, members of Fedora Chinese Users Group have wishes that:

1. Setting up a option (switch) to always show single character as preferred candidates before phrases.
2. Setting up a shortcut key or option (switch) to toggle between GB18030 and CJK extended character set.
3. Providing a tool to integrate users's custom phrases into the (internal) code table and the feature that exporting it to a code table file in plain text format.

Thanks.

[mike-fabian]

I made new issues for these three things to organize the work better:

1. Setting up a option (switch) to always show single character as preferred candidates before phrases.

https://github.com/mike-fabian/ibus-table/issues/107

2. Setting up a shortcut key or option (switch) to toggle between GB18030 and CJK extended character set.

https://github.com/mike-fabian/ibus-table/issues/108

3. Providing a tool to integrate users's custom phrases into the (internal) code table and the feature that exporting it to a code table file in plain text format.

https://github.com/mike-fabian/ibus-table/issues/109

So what remains in this issue here is improving the pinyin support of ibus-table.