Hi Boyuan, On Mon, Jun 29, 2026 at 4:05 PM Boyuan Yang <[email protected]> wrote: > I had some work on splitting the two packages, and it has passed the NEW queue > again and was made available in Debian Unstable. I tested on my local VMs, and > they seem to work well either individually or together. I believe this should > have solved the issue as ibus-libbopomofo will not be pre-installed in any way > either via Live systems or standard tasksel. Please let me know if there > are any further issues around it.
Thank you very much for the great work on splitting the package so quickly. I think this completely resolved the pre-installation issue in Debian Live and tasksel to improve the out of box user experience. However, during my tests of the ibus-libbopomofo individually, I noticed some technical limitation regarding the locale mapping itself. Even though the package is no longer pre-installed, it still maps itself to the zh_TW locale in its metadata. If user manually installs it or other package recommends, it still gets enabled by default under zh_TW locale. Due to it's based on a Simplified Chinese database engine libpinyin, it uses an automated converter (like OpenCC) to force convert to Traditional Chinese output, zh_TW user may still facing to some issues like: - missed a large amount of the native character set - non localized vocabulary and phrases - different pronunciation rules under zh_TW locale - mismatch typing order logic for native typing habits...etc. Native input methods like Chewing and Zhuyin allow users to input symbols in combinations and sequences that differ from standard Pinyin structures. Because libbopomofo is mapping Bopomofo symbols onto a Pinyin-based engine to process, it gets confused by these native typing habits and completely messes up the output when native zh_TW user type. Forcing Traditional Chinese output under zh_TW locale unfortunately do not satisfy native zh_TW users but causes confusion and usability issues. Since the libbopomofo cannot fit the needs for native user under zh_TW locale, keeping the zh_TW mapping in the XML metadata might still confuses users. Would it be possible to remove the zh_TW locale mapping from the metadata entirely, leaving it available for manual configuration without enabled by default under zh_TW locale? In fact, during my tests, this is much more suitable for bopomofo input method users who need to type Simplified Chinese under the zh_CN locale. Because its built-in database is designed based libpinyin, it contains the correct vocabulary, phrases for zh_CN. Please let me know if you would prefer me to open a new bug report to track this specific metadata adjustment for zh_TW locale? Best regards, -- -Andrew
