From: LdBeth <andpuke@foxmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: LdBeth <andpuke@foxmail.com>, 52792@debbugs.gnu.org
Subject: bug#52792: 27.2; please don't hardcode utf-8 when fetching group list
Date: Sun, 26 Dec 2021 17:49:56 +0800 [thread overview]
Message-ID: <tencent_F5E67412AC4AFEE6DC70BAC31C9F7A4C3009@qq.com> (raw)
In-Reply-To: <83tuevq28p.fsf@gnu.org>
>>>>> In <83tuevq28p.fsf@gnu.org>
>>>>> Eli Zaretskii <eliz@gnu.org> wrote:
> Thanks, but this is not the right way to solve such problems, IMO. We
> should either make the coding-system be customizable as a simple
> value, or (better) have a more complex data structure that allows to
> specify the encoding for each NNTP server (or for servers matching
> some regexp), with UTF-8 being the default.
Right, it would be more desirable to use UTF-8 internally, rather than
doing ad-hoc encoding translation everywhere.
> Also, AFAICT, Gnus currently uses more than a single variable to hold
> the coding-system it uses for decoding stuff in different situations,
> so some changes will probably be needed to use a single customizable
> value everywhere.
Currently the encode/decode functions in message.el works fine for
GBK, this bug would not affect people who are only using Gnus for
IMAP/Maildir. It would still better leaving these two systems (News
and Messages) separated. Today most email services are already
switched to UTF-8. It's only that many NNTP servers are still using
the old encoding for legacy reasons.
--
LDB
prev parent reply other threads:[~2021-12-26 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 16:19 bug#52792: 27.2; please don't hardcode utf-8 when fetching group list LdBeth
2021-12-26 2:00 ` LdBeth
2021-12-26 2:25 ` LdBeth
2021-12-26 7:00 ` Eli Zaretskii
2021-12-26 9:49 ` LdBeth [this message]
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=tencent_F5E67412AC4AFEE6DC70BAC31C9F7A4C3009@qq.com \
--to=andpuke@foxmail.com \
--cc=52792@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.