unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: LdBeth <andpuke@foxmail.com>
Cc: 52792@debbugs.gnu.org
Subject: bug#52792: 27.2; please don't hardcode utf-8 when fetching group list
Date: Sun, 26 Dec 2021 09:00:54 +0200	[thread overview]
Message-ID: <83tuevq28p.fsf@gnu.org> (raw)
In-Reply-To: <tencent_03F53C61E4EB9C58CDFE99B951775739820A@qq.com> (message from LdBeth on Sun, 26 Dec 2021 10:00:42 +0800)

> Date: Sun, 26 Dec 2021 10:00:42 +0800
> From: LdBeth <andpuke@foxmail.com>
> 
> This patch that reverts only related changes (and does nothing else)
> in cb12a84f2c519a48dd87453c925e3bc36d9944db should make Gnus works
> again for none utf-8 NNTP servers.

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.

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.





  parent reply	other threads:[~2021-12-26  7:00 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 [this message]
2021-12-26  9:49     ` LdBeth

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83tuevq28p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52792@debbugs.gnu.org \
    --cc=andpuke@foxmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).