From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: gnus-uu-digest-(mail|post)-forward
Date: Mon, 07 Oct 2002 17:07:56 +0900 [thread overview]
Message-ID: <yotly99a4qoz.fsf@jpl.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Hi,
Execution of the command gnus-uu-digest-(mail|post)-forward on a
summary line will generate the form of a message body as follows:
--8<---------------cut here---------------start------------->8---
< #multipart type=digest >
< #part type=message/rfc822 >
Subject: Topics
Topics:
subject string of an article
< #mml type=message/rfc822 >
header of an article
body of an article
--8<---------------cut here---------------end--------------->8---
There's a problem that the first `Topics' part may contain non-
ascii subject string, and it will be sent without being encoded.
Though I requested in the past and had changed the tag into #mml
from #part, it has been returned after that. Probably, some
another problems occurred. Then, I make a different proposal
from last time.
Isn't it possible to change the type of the first `Topics' part
from `message/rfc822' to `text/plain'? If it is allowed, the
code can be changed as follows and the problem will be solved.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 475 bytes --]
--- gnus-uu.el~ 2002-04-12 11:46:57 +0000
+++ gnus-uu.el 2002-10-07 08:03:29 +0000
@@ -836,7 +836,7 @@
"Date: %s\nFrom: %s\nSubject: %s Digest\n\n"
(current-time-string) name name))
(when (and message-forward-as-mime gnus-uu-digest-buffer)
- (insert "< #part type=message/rfc822 >\nSubject: Topics\n\n"))
+ (insert "< #part type=text/plain >\n"))
(insert "Topics:\n")))
(when (not (eq in-state 'end))
(setq state (list 'middle))))
next reply other threads:[~2002-10-07 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 8:07 Katsumi Yamaoka [this message]
2002-10-10 11:12 ` gnus-uu-digest-(mail|post)-forward Katsumi Yamaoka
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=yotly99a4qoz.fsf@jpl.org \
--to=yamaoka@jpl.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.
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).