New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/pull/29981#issuecomment-813129721

Comment:
> @sgn
> 
> I'm sorry, I was unclear.

Sorry, It was me the one was unclear.

> It isn't the EUC-JP support that is broken. In fact, my change removes EUC-JP support. The problem is that the newer versions of anthy output UTF-8, whereas the anthy backend to uim takes EUC-JP, preventing the correct conversion of kanji. Instead, the anthy-utf8 backend must be used with newer versions of anthy. That is why this change disables the backend meant to interface with old (EUC-JP) anthy.

I understood your arguments.
However, removing euc-jp looks like too arbitrary to me.
Debian had also [removed euc-jp supports for a while][1] then [restore euc-jp support][2] because [bug #953616][bug]

Quoted from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9536161

> - 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.


[1]: https://salsa.debian.org/debian/uim/-/commit/d678ee362b87bfcb512d9275b4eadcc5932a3e10
[2]: https://salsa.debian.org/debian/uim/-/commit/265f012072277cc7c67abf4fda232d9a933e7d41
[bug]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953616