From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: uim: disable non-utf-8 anthy backend
Date: Mon, 05 Apr 2021 02:55:39 +0200 [thread overview]
Message-ID: <20210405005539.hqBZQbHk83MTCd9Sd-8FHrK6769ilUVymDrywICx-ek@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: 1414 bytes --]
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
next prev parent reply other threads:[~2021-04-05 0:55 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 [this message]
2021-04-05 0:56 ` sgn
2021-04-05 2:04 ` Gorggg
2021-04-05 2:04 ` Gorggg
2021-04-05 2:05 ` Gorggg
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=20210405005539.hqBZQbHk83MTCd9Sd-8FHrK6769ilUVymDrywICx-ek@z \
--to=sgn@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).