Used the Intelligent Pinyin method for inputting some Chinese characters. Didn't observe any oddities.
fcitx-libpinyin and ibus-libzhuyin
----------------------------------
Installed fcitx-libpinyin 0.5.3-1 and ibus-libzhuyin 1.8.2-1 from bionic-release, and libzhuyin13 2.2.2-1~ubuntu18.04.1 from bionic-proposed.
Used
- the Pinyin (LibPinyin) (Fcitx) method (on Unity)
- the New Zhuyin method
for inputting some Chinese characters. Didn't observe any issues due to the upgraded packages built from libpinyin.
Successfully rebuilt the bionic-release versions of fcitx-libpinyin and ibus-libzhuyin with libpinyin 2.2.2.
Conclusion: We can stay with the current bionic versions of fcitx-libpinyin and ibus-libzhuyin. Upgrading those would be beyond the scope of this bug.
I have done these tests:
bionic
------
Installed from bionic-proposed these packages:
* ibus-libpinyin 1.11.0- 1ubuntu0. 18.04.1 ubuntu18. 04.1 ubuntu18. 04.1
* libpinyin-data 2.2.2-1~
* libpinyin13 2.2.2-1~
Used the Intelligent Pinyin method for inputting some Chinese characters. Didn't observe any oddities. Bug #1829947 is not present (as expected).
cosmic
------
Installed from cosmic-proposed these packages:
* ibus-libpinyin 1.11.0- 1ubuntu0. 18.10.1 ubuntu18. 10.1 ubuntu18. 10.1
* libpinyin-data 2.2.2-1~
* libpinyin13 2.2.2-1~
Used the Intelligent Pinyin method for inputting some Chinese characters. Didn't observe any oddities.
fcitx-libpinyin and ibus-libzhuyin ------- ------- ------- ------ ubuntu18. 04.1 from bionic-proposed.
-------
Installed fcitx-libpinyin 0.5.3-1 and ibus-libzhuyin 1.8.2-1 from bionic-release, and libzhuyin13 2.2.2-1~
Used
- the Pinyin (LibPinyin) (Fcitx) method (on Unity)
- the New Zhuyin method
for inputting some Chinese characters. Didn't observe any issues due to the upgraded packages built from libpinyin.
Successfully rebuilt the bionic-release versions of fcitx-libpinyin and ibus-libzhuyin with libpinyin 2.2.2.
Conclusion: We can stay with the current bionic versions of fcitx-libpinyin and ibus-libzhuyin. Upgrading those would be beyond the scope of this bug.