gnus-draft-send and rfc2047-encode-encoded-words/rfc2047-encodable-p

gnus-draft-send and rfc2047-encode-encoded-words/rfc2047-encodable-p

[Reiner Steib]

Hi,

in `gnus-draft-send', `rfc2047-encode-encoded-words' is let-bound to
nil.  When I compose a message with Subject "foo=?bar abc baz=?blubb",
I get to differently encoded subjects in the sent messages: Sent
directly from the message composition buffer, I get the following raw
header:

| Subject: =?us-ascii?Q?foo=3D=3Fbar?= abc =?us-ascii?Q?baz=3D=3Fblubb?=

When I save do `C-c C-d' (`message-dont-send') first and then send the
message from the drafts group using `D s', I get:

| Subject: foo=?bar abc baz=?blubb

Does anyone see a reason for let-binding
`rfc2047-encode-encoded-words' there?  We should probably add a
comment in the code explaining the rationale.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: gnus-draft-send and rfc2047-encode-encoded-words/rfc2047-encodable-p

[Katsumi Yamaoka]

>>>>> In <v9hcx6ta0p.fsf@marauder.physik.uni-ulm.de>
>>>>>	Reiner Steib wrote:

> Does anyone see a reason for let-binding
> `rfc2047-encode-encoded-words' there?  We should probably add a
> comment in the code explaining the rationale.

I don't know the reason to bind it there.  AFAIK, drafts are
encoded according to only `message-draft-coding-system', not
RFC2047, and saved.  What should be fixed is the code which uses
the RFC2047 encoding to save drafts, if any.  I agree to remove
it.

Regards,