From: Gorggg <Gorggg@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: uim: disable non-utf-8 anthy backend
Date: Mon, 05 Apr 2021 04:05:26 +0200 [thread overview]
Message-ID: <20210405020526.3ESKaEoeAUPAlWuUoeZppk80373PvQbgPO60q3MP7B8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29981@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
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.
next prev parent reply other threads:[~2021-04-05 2:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 20:15 [PR PATCH] " Gorggg
2021-04-03 22:01 ` ericonr
2021-04-04 15:45 ` sgn
2021-04-04 19:47 ` Gorggg
2021-04-04 19:49 ` [PR PATCH] [Updated] " Gorggg
2021-04-04 19:50 ` Gorggg
2021-04-05 0:55 ` sgn
2021-04-05 0:55 ` sgn
2021-04-05 0:56 ` sgn
2021-04-05 2:04 ` Gorggg
2021-04-05 2:04 ` Gorggg
2021-04-05 2:05 ` Gorggg [this message]
2021-04-05 2:25 ` Gorggg
2021-04-06 12:23 ` sgn
2021-04-06 16:02 ` Gorggg
2021-04-07 0:15 ` sgn
2021-04-14 23:47 ` sgn
2021-04-15 14:39 ` [PR PATCH] [Closed]: " sgn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210405020526.3ESKaEoeAUPAlWuUoeZppk80373PvQbgPO60q3MP7B8@z \
--to=gorggg@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).