From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45925@debbugs.gnu.org
Subject: bug#45925: 27.1; *Summary* buffer vs. raw utf-8 headers
Date: Wed, 20 Jan 2021 13:58:08 +0800 [thread overview]
Message-ID: <87zh14f8un.5.fsf@jidanni.org> (raw)
In-Reply-To: <87ft30azwi.5.fsf@jidanni.org>
>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
LI> 積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
>> Try this simple experiment:
>> $ echo Subject: 一二三|procmail
>> $ echo Subject: 一二三|iconv -t big5|procmail
LI> I don't have procmail installed, so I'm not sure what these do -- are
LI> you sending a mail (to yourself?) here? Do you have a recipe to
LI> reproduce this problem without the use of procmail?
$ echo Subject: 一二三 > ~/Maildir/new/Z
$ file ~/Maildir/new/Z
~/Maildir/new/Z: UTF-8 Unicode text
>> $ emacs -f gnus
>>
>> In the *Article* buffer, both look like
>> Subject: 一二三
>> In the *Summary* buffer so does the big5 version.
>> Alas, the utf-8 version looks like
>> c\x80\xd3....
>>
>> (Yes, these are illegal raw headers. But Gnus is supposed to be
>> accommodating. And it does... but oddly not for the majority (UTF-8) case.)
LI> [...]
>> (Might be related to bug#45724.)
LI> Is this still with nnml? If so, could you find the resulting lines in
LI> the .overview files in the nnml directory and post them here? (Perhaps
LI> after gzipping them to avoid Emacs helpfully re-encoding the lines.)
Yes, nnml.
The headers get appended raw to .overview.
Thus .overview contains a mix of ASCII, big5, and UTF-8, all in the same file.
$ echo Subject: 一二三|iconv -t big5 > ~/Maildir/new/B5
$ echo Subject: 一二三 > ~/Maildir/new/UT
$ emacs -f gnus
$ tail -n 2 Mail/mail/misc/.overview|qprint -e
37397 =A4@=A4G=A4T (nobody) <87a6t4gnpx.5.fsf@totally-fudged-out-mess=
age-id> 0 0 Xref: jidanni5 mail.misc:37397=09
37398 =E4=B8=80=E4=BA=8C=E4=B8=89 (nobody) <878s8ognpx.5.fsf@totally-=
fudged-out-message-id> 0 0 Xref: jidanni5 mail.misc:37398=09
Anyway: *Summary* oddly can only deal with raw big5, not raw UTF-8.
However *Article* can deal with both.
next prev parent reply other threads:[~2021-01-20 5:58 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 [this message]
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
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=87zh14f8un.5.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=45925@debbugs.gnu.org \
--cc=larsi@gnus.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 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).