Bug#953616: uim-data: anthy.scm and anthy-custom.scm missing, so can't use EUC-JP
On Sun, Jun 07, 2020 at 06:21:56PM +0900, OZAKI Masanobu / 尾崎正伸 wrote: > > After upgrading to Buster, I found uim-anthy no longer works as it was: no > > conversion were carried out in ja_JP.euc-jp locale from any uim-related > > clients. I have not tried ja_JP.utf-8 locale yet, because my files is > > very fermented after over-20-years use.:( > > I succeeded in solving the problem: > - anthy-utf8 works with ja_JP.eucJP locale if set up properly. > - If you have customized enabled-im-list on "stretch" system (in > ~/.uim.d/customs/custom-global.scm) with uim-pref-gtk or other tools, > uim sticks to use anthy instead of anthy-utf8 and fails kanji-conversion > on upgraded "buster" system. > > Thus I believe that users should be warned in some document or upgrade > information to check the uim-pref-*'s "Enabled input methods" entry. I am so sorry for the inconvenience and my too late replying. I removed anthy for EUC-JP at 2017-09 before Buster release (2019-07): * https://salsa.debian.org/debian/uim/-/commit/d678ee362b87bfcb512d9275b4eadcc5932a3e10 * https://salsa.debian.org/debian/uim/-/commit/e39275ce8efedee8ff52c3a260a4e0073a6e400d I do not use anthy and EUC-JP (my all files have been converted to UTF-8), so I cannot think of them, sorry. Nokubi-san, YOSHINO-san, can we just resurrect anthy EUC-JP? -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E signature.asc Description: PGP signature
Bug#953616: uim-data: anthy.scm and anthy-custom.scm missing, so can't use EUC-JP
Hello, > After upgrading to Buster, I found uim-anthy no longer works as it was: no > conversion were carried out in ja_JP.euc-jp locale from any uim-related > clients. I have not tried ja_JP.utf-8 locale yet, because my files is > very fermented after over-20-years use.:( I succeeded in solving the problem: - anthy-utf8 works with ja_JP.eucJP locale if set up properly. - If you have customized enabled-im-list on "stretch" system (in ~/.uim.d/customs/custom-global.scm) with uim-pref-gtk or other tools, uim sticks to use anthy instead of anthy-utf8 and fails kanji-conversion on upgraded "buster" system. Thus I believe that users should be warned in some document or upgrade information to check the uim-pref-*'s "Enabled input methods" entry. Thanks, Masanobu Ozaki
Bug#953616: uim-data: anthy.scm and anthy-custom.scm missing, so can't use EUC-JP
Package: uim-data Version: 1:1.8.8-4+deb10u2 Severity: normal Tags: l10n Dear Maintainer, After upgrading to Buster, I found uim-anthy no longer works as it was: no conversion were carried out in ja_JP.euc-jp locale from any uim-related clients. I have not tried ja_JP.utf-8 locale yet, because my files is very fermented after over-20-years use.:( Anyway, I found that anthy.scm and anthy-custom.scm are missing in /usr/share/uim/, and copying them from the uim-anthy package of stretch looks to fix my problem. So, I appreciate if these files (and other related ones if necessary) are restored in the package, while I know that Debian dropped, or at least is about to drop, UTF-8 support. Sincerely, Masanobu Ozaki -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ja_JP.eucJP, LC_CTYPE=ja_JP.eucJP (charmap=EUC-JP), LANGUAGE=ja_JP.eucJP (charmap=EUC-JP) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages uim-data depends on: ii libuim-data 1:1.8.8-4+deb10u2 ii m17n-db 1.8.0-1 uim-data recommends no packages. uim-data suggests no packages. -- no debconf information
