What version of the product are you using? On what operating system?
OS (Linux distributions, UNIX or ...): Debian
Architecture (i386, x86_64): i386
IBus version: 1.4.1-7
Input method name and version: wubi-jidian86, wubi-haifeng86 (current
versions, as supplied by Debian)
Python version: 2.7.3rc2
dbus version: 1.6.0-1
dbus-python version: 1.1.1-1
gtk version (if bug is about gtk applications):
qt version (if bug is about qt applications):
What steps will reproduce the problem?
1. Switch Wubi on in some input field
2. Try to write this character: 晞 (Code = JQDH)
What is the expected output? What do you see instead?
Instead of seeing the character, I see the wubi code in the input window,
Please provide any additional information below.
The character itself is present in the table's input file in the source
code, but I cannot write it. The other Wubi input method in ibus doesn't
allow me to write it, either. I can put the character in using
Google-PinYin, however, so it's really a problem with the code related to
the two Wubi input methods.
This appears to work, though using this feature is highly opaque: There is
no GUI for it - not on my system, anyways, and no way to discover which
options might be available, or which one is currently active. After finding
that the various modes can be cycled through using Ctrl-;, I arrived at
being able to write that character after some trial-and-error. Please take
the confirmation of my bug report by native speakers of Chinese as an
indication that the user interface for these features definitely leaves
something to be desired.
Until I saw your message, I had "Embedded in menu" for the "Show language
panel" mode. Now I have changed this to "Always". Is there an easy way to
find this "18.104.22.16821003" release, short of browsing all tags in the
several github projects?
Yes, but I would like to quickly gain an overview of what changed, like
maybe an overview page including the changelogs of all subpackages. I
can 'git clone' all packages, then go through 'git log' for each one, but
it there was an easier way...