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

Bug#898233: fcitx-libpinyin: No Traditional Chinese for Bopomofo (Zhuyin)



Package: fcitx-libpinyin
Version: 0.5.3-1
Severity: important
Tags: l10n

Dear Maintainer,

I recently upgraded from stretch to buster, and discovered that
fcitx-zhuyin was superseded by fcitx-libpinyin.

With “Bopomofo (LibPinyin)”, the candidate character menu (and output)
appears in Simplified Chinese. I have tried selecting “Traditional
Chinese” from fcitx’s taskbar menu, but that does not change the
behavior of the program. (Moreover, Traditional Chinese should be the
default setting for the Bopomofo input method, since it is used
predominantly in Taiwan.)

I did not encounter this problem with “Bopomofo (Zhuyin)”.

I’m not sure if this is important, but the only other fcitx input method
I have installed is fcitx-table-cangjie5.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fcitx-libpinyin depends on:
ii  libc6                    2.27-3
ii  libdbus-1-3              1.12.6-2
ii  libfcitx-config4         1:4.2.9.6-2
ii  libfcitx-qt5-1           1.2.2-2
ii  libfcitx-utils0          1:4.2.9.6-2
ii  libgcc1                  1:8.1.0-1
ii  libglib2.0-0             2.56.1-2
ii  libpinyin-data           2.2.0-1
ii  libpinyin13              2.2.0-1
ii  libqt5core5a             5.10.1+dfsg-5
ii  libqt5dbus5              5.10.1+dfsg-5
ii  libqt5gui5               5.10.1+dfsg-5
ii  libqt5network5           5.10.1+dfsg-5
ii  libqt5webenginewidgets5  5.10.1+dfsg-3
ii  libqt5widgets5           5.10.1+dfsg-5
ii  libstdc++6               8.1.0-1

fcitx-libpinyin recommends no packages.

fcitx-libpinyin suggests no packages.

-- no debconf information

Reply to: