Direction of ibus-table/ibus-table的發展方向

22 views

Skip to first unread message

Ma Xiaojun

unread,

Jul 1, 2012, 7:52:43 AM7/1/12

to ibus...@googlegroups.com

Hi, all.
大家好。

I'm a new member of the IBus project.
我是IBus項目的新成員。
I've spent some time categorizing (assigning component) of all open
issues of IBus.
我花了一些時間給IBus的open issues分類（指定component）
My current interest is ibus-table, since it is criticized most in the community.
我當前的興趣是ibus-table，因為它是在社區中受到最多批評的。
I've done some commits on my github.
我在我的github上做了一些commit。
https://github.com/maxiaojun/ibus-table/commits/master

I just discovered that if ibus-table doesn't respect SCIM format table
data fully.
我剛剛發現，ibus-table並不完全受SCIM格式的table數據選項指示。

For example, SCIM Quick has at most 9 candidates while SCIM Cangjie
has at most 10 candidates.
例如，SCIM速成最多有9個候選詞，而SCIM速成最多有10個候選詞。
In table, it is, respectively:
在table中，分別是：
SELECT_KEYS = 1,2,3,4,5,6,7,8,9
SELECT_KEYS = 1,2,3,4,5,6,7,8,9,0

We inherited same option from SCIM.
我們從SCIM繼承了相同的選項。
But ibus-table always give at most 6 candidates.
但ibus-table總是給出最多6個候選詞。
http://code.google.com/p/ibus/issues/detail?id=1474

So I think we need to make a decision now.
所以我想我們現在需要做出一個決定。

1. Try to make ibus-table more SCIM compatible, respect existing
options strictly.
1. 使ibus-table和SCIM更加兼容，嚴格執行已有的選項。
2. Try to make ibus-table more flexible and try minimize the change of
default behavior.
2. 使ibus-table更加靈活，也使默認行為的變化儘可能小。

Bugs caused by not respecting SCIM options (may not complete):
由不執行SCIM選項導致的Bugs（可能不全面）:
http://code.google.com/p/ibus/issues/detail?id=155
http://code.google.com/p/ibus/issues/detail?id=622
http://code.google.com/p/ibus/issues/detail?id=788
http://code.google.com/p/ibus/issues/detail?id=795
http://code.google.com/p/ibus/issues/detail?id=1307
http://code.google.com/p/ibus/issues/detail?id=1373
http://code.google.com/p/ibus/issues/detail?id=1474