[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#891954: ibus-libpinyin can't select character candidate except the first one.



I feel this is a bug deserving more than "severity: normal", given that it almost completely destroys the OS's ability to input chinese characters. The fact that the workaround also destroys the cache of input training data is not great either.

Furthermore, the fact that the only mention of the workaround is in this thread and an AskUbuntu page, laypeople are going to need quite a bit of luck to find this.

On Fri, 02 Mar 2018 22:41:40 -0500 Bo Lan <lanbo64@gmail.com> wrote:

> Package: ibus-libpinyin
> Version: 1.9.2-2
> Severity: normal
>
> Dear Maintainer,
>
> The ibus-libpinyin (Intelligent Pinyin) is not be able to select character
> candidate other than the first one.
>
> Once I input a pinyin for a Chinese character, by default, there are 5
> candidates can be selected. If I need the first candidate, I can press 1 or
> space on the keyboard to select it. It works. If I need one of the 2nd to 5th
> candidates, however, I need to press 2 to 5 to select, and it doesn't work.
>
> One pinyin can have many of characters, if we can select only one, the program
> is not usable.
>
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers testing
> APT policy: (500, 'testing'), (100, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages ibus-libpinyin depends on:
> ii ibus 1.5.17-3
> ii libc6 2.26-6
> ii libgcc1 1:8-20180218-1
> ii libglib2.0-0 2.54.3-2
> ii libibus-1.0-5 1.5.17-3
> ii libpinyin13 2.1.91-1
> ii libsqlite3-0 3.22.0-1
> ii libstdc++6 8-20180218-1
> ii python3 3.6.4-1
> ii python3-gi 3.26.1-2
>
> ibus-libpinyin recommends no packages.
>
> ibus-libpinyin suggests no packages.
>
> -- no debconf information
>
>


Reply to: