https://bugzilla.redhat.com/show_bug.cgi?id=834971
--- Comment #8 from James Ni <jni(a)redhat.com> ---
Hi Mathieu, Jens
As caius mentioned in his comment:
"In SCIM, it demonstrated the true purposes of Chinese filter (on Cangjie /
Quick / anything) - users can input in either Traditional or Simplified Chinese
key combinations, and able to output the characters of in each other's
standards."
I just investige a bit of ibus-table, I found that actually ibus-table had
provide such kind of filter. Indeed, the ibus-table have filters such as
"Simplified Chinese only" and "Traditional Chinese only", but it also
provide a
filter allow both simplified chinese and tranditional chinese passed.
In upstream,
https://github.com/acevery/ibus-table/blob/master/engine/table.py,
from line 96 to line 101, five candidate filter mode have defined for
ibus-table
# self._chinese_mode: the candidate filter mode,
# 0 is simplify Chinese
# 1 is traditional Chinese
# 2 is Big charset mode, but simplify Chinese first
# 3 is Big charset mode, but traditional Chinese first
# 4 is Big charset mode.
So, mode 4 could be used by hong kong user if they want to input Simplified
Chinese and Traditional Chinese at same time, or they can choose mode 2 and 3,
both should be ok. I test the input rji and yri in mode 4, the output is
correct.
The attachment is the screenshot, which you can see, user could switch these 5
modes by clicking the second button in UI.
The test enviroment:
ibus-table-chinese-cangjie-1.3.5-1.fc16
ibus-table-1.3.9.20110827-1.fc16.noarch
OS: Fedora 16
Locale: en_US.utf8
For tranditional chinese user, the default value of mode is 1. so if the hong
kong user wanted, we can change default value of mode to 4, then i think the
issue should be resolved.
Please correct me if i understand the issue wrong. Thanks
--
You are receiving this mail because:
You are on the CC list for the bug.