From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Gnus; Restore multi encoding support for NNTP
Date: Tue, 28 Dec 2021 15:31:07 +0100 [thread overview]
Message-ID: <87ilv8ajis.fsf@gnus.org> (raw)
In-Reply-To: <87r19x2zar.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 27 Dec 2021 19:17:32 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> What's worse is when there are two group names having different coding
>> systems decoded to the same UTF-8 string for the same server, if gnus
>> doesn't correctly record which one uses which, well... (This is the
>> reason for using charset string property for that)
>
> Gnus does not handle this situation correctly, and I can't imagine it
> ever did.
I think it did, since we just kept the unencoded data in the newsrc
alist, and then decoded before displaying. So you could have any number
of groups with names that decoded to the same displayed string.
> But probably it should. How does this per-group encoding
> information arrive from the server?
It doesn't -- you just have to know (and put that knowledge in
`gnus-group-name-charset-group-alist').
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-28 14:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 9:42 Gnus; Restore multi encoding support for NNTP LdBeth
2021-12-27 12:11 ` Lars Ingebrigtsen
2021-12-27 12:41 ` LdBeth
2021-12-27 12:57 ` Lars Ingebrigtsen
2021-12-27 13:58 ` LdBeth
2021-12-28 3:17 ` Eric Abrahamsen
2021-12-28 14:31 ` Lars Ingebrigtsen [this message]
2021-12-28 15:40 ` LdBeth
2021-12-28 14:29 ` Lars Ingebrigtsen
2021-12-28 15:43 ` LdBeth
2021-12-30 10:23 ` [PATCH] " LdBeth
2021-12-30 14:49 ` Lars Ingebrigtsen
2021-12-30 14:54 ` Eli Zaretskii
2021-12-30 15:18 ` LdBeth
2021-12-31 15:59 ` Lars Ingebrigtsen
2022-01-01 2:11 ` LdBeth
2022-01-01 3:32 ` LdBeth
2022-01-03 11:18 ` Lars Ingebrigtsen
2022-01-03 11:25 ` Lars Ingebrigtsen
2022-01-03 14:00 ` LdBeth
2022-01-01 6:58 ` Eli Zaretskii
2022-01-01 8:34 ` LdBeth
2022-01-01 8:56 ` Eli Zaretskii
2022-01-01 9:26 ` LdBeth
2022-01-01 9:35 ` Eli Zaretskii
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=87ilv8ajis.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).