New comment by Gorggg on void-packages repository

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

Comment:
@sgn 

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

This sounds like exactly the issue I had. I had added the conventional anthy backend (which used EUC-JP) to the custom im list. When I upgraded, kanji conversion failed because uim was still using the old backend even when anthy was upgraded to a UTF-8 version. That was what prompted me to submit this fix.

I guess this change is a bit selfish for my particular case, it was just very difficult to figure out why kanji input was suddenly no longer working and I wanted to spare other people that trouble.

Thank you for your time in addressing this.