From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: [0.95] those nasty \201s again: test example
Date: 07 Aug 1999 00:13:50 +0400 [thread overview]
Message-ID: <m31zdgk6pt.fsf@vvv.vsu.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 30 bytes --]
Hi,
here is a test message:
[-- Attachment #2: Type: text/plain, Size: 845 bytes --]
>From owner-qqq-digest-outgoing@bbb.ccc Sun Aug 1 10:00:00 1999
From: owner-qqq-digest@bbb.ccc
To: qqq-digest@bbb.ccc
Subject: qqq-digest V7 #1234
Date: Sun, 1 Aug 1999 10:00:00
qqq-digest Friday, 6 August 1999 Volume 07 : Number 1234
In this issue:
subj1
subj2
subj3
----------------------------------------------------------------------
From: aa1@bbb.ccc
Date: Sun, 1 Aug 1999 01:00:00 -0500 (EST)
Subject: subj1
some text
------------------------------
From: =?iso-8859-1?q?Gr=FC=DF?= Gott <aa2@bbb.ccc>
Date: Sun, 01 Aug 1999 02:00:00 KST
Subject: =?iso-8859-1?q?Gr=FC=DF?= Gott
some text
------------------------------
From: aa3@bbb.ccc
Date: Sun, 01 Aug 1999 03:00:00 -0700
Subject: subj3
some text
------------------------------
End of qqq-digest V7 #1234
***********************************
trailer
[-- Attachment #3: Type: text/plain, Size: 669 bytes --]
1) save it to file, say, test.txt
2) cat test.txt test.txt >> /var/spool/mail/$USER
(more than one mail is important!)
3) receive the mail with gnus (i used nnmbox backend)
4) mark both messages using hash (#)
5) press C-M-d
then the summary buffer for these digests looks like:
[ 1: aa1@bbb.ccc ] subj1
< 1: aa1@bbb.ccc >
[ 1: Gr\201Э\201ъ Gott ] Gr\201Э\201ъ Gott
< 1: Gr\201Э\201ъ Gott >
[ 1: aa3@bbb.ccc ] subj3
< 1: aa3@bbb.ccc >
something is wrong with handling of multibyte buffers in gnus.
such problems appear quite regularly... :-(
Best regards, -- Vladimir.
next reply other threads:[~1999-08-06 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-06 20:13 Vladimir Volovich [this message]
1999-08-06 23:30 ` Shenghuo ZHU
1999-08-07 22:05 ` Jack Vinson
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=m31zdgk6pt.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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.
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 NNTP newsgroup(s).