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
