all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45925@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#45925: 27.1; *Summary* buffer vs. raw utf-8 headers
Date: Fri, 22 Jan 2021 19:06:00 +0100	[thread overview]
Message-ID: <87h7n826ev.fsf@gnus.org> (raw)
In-Reply-To: <83v9bq59b3.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 21 Jan 2021 22:22:56 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Why do you expect a mixed-encoding stuff to work in Emacs?  Emacs only
> supports a single encoding of any chunk of text it gets, be it a file
> or an email message.
>
> Files such as this one are simply not supported.

Sure they are.  It's not a text file; it's an octet stream.

But as Dan points out, Gnus doesn't handle these invalid mails
optimally, and doing some RFC2047-encoding to the headers before writing
the .overview file will help a bit here, so I've now done that in Emacs
28.

(Gnus will still display some of these headers "wrong" in the summary
buffer, and display them "right" in the article buffer, because Gnus has
to guess at what the charset is, and it does further guessing in the
article buffer than in the summary buffer, for reasons of efficiency.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-01-22 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-17  5:35 bug#45925: 27.1; *Summary* buffer vs. raw utf-8 headers 積丹尼 Dan Jacobson
2021-01-19  5:30 ` Lars Ingebrigtsen
2021-01-20  5:58   ` 積丹尼 Dan Jacobson
2021-01-20 16:31     ` Lars Ingebrigtsen
2021-01-21 19:55       ` 積丹尼 Dan Jacobson
2021-01-21 20:22         ` Eli Zaretskii
2021-01-21 20:54           ` 積丹尼 Dan Jacobson
2021-01-22 18:06           ` Lars Ingebrigtsen [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=87h7n826ev.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=45925@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jidanni@jidanni.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.