Gnus development mailing list
 help / color / mirror / Atom feed
From: Romain FRANCOISE <romain@orebokech.com>
Subject: Re: iso-8859-2 characters are broken in forwarded messages.
Date: Sat, 18 Oct 2003 11:58:15 +0200	[thread overview]
Message-ID: <877k32q348.fsf@orebokech.com> (raw)
In-Reply-To: <ilu65innwgr.fsf@extundo.com> (Simon Josefsson's message of "Sat, 18 Oct 2003 03:52:36 +0200")

Simon Josefsson <jas@extundo.com> writes:

> So if forwarding messages stops working for anyone, please holler.

There is a small logic error: it does both m-f-make-body-mml and
m-f-make-body-plain, resulting in a strange message buffer.  The
following patch fixes things for me.

(I hand-edited this patch because I have other uncommitted changes in
message.el, it may not work.)

-- 
Romain FRANCOISE <romain@orebokech.com> | They're nothing but scared
it's a miracle -- http://orebokech.com/ | little mice.

Index: message.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/message.el,v
retrieving revision 6.370
diff -u -r6.370 message.el
--- message.el	18 Oct 2003 03:27:46 -0000	6.370
+++ message.el	18 Oct 2003 09:54:22 -0000
@@ -6091,8 +6090,8 @@
 			      "Content-Type: *multipart/\\(signed\\|encrypted\\)"
 			      nil t)))))
 	    (message-forward-make-body-mml forward-buffer)
-	  (message-forward-make-body-mime forward-buffer)))
-    (message-forward-make-body-plain forward-buffer))
+	  (message-forward-make-body-mime forward-buffer))
+      (message-forward-make-body-plain forward-buffer)))
   (message-position-point))
 
 ;;;###autoload



  parent reply	other threads:[~2003-10-18  9:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <hhsmluupo1.fsf@blah.pl>
2003-10-15 22:26 ` Reiner Steib
     [not found]   ` <hhy8vm13yn.fsf@blah.pl>
2003-10-16  1:21     ` Simon Josefsson
     [not found]       ` <hhekxeym1t.fsf@blah.pl>
2003-10-16  4:34         ` Simon Josefsson
2003-10-17 16:59           ` Lars Magne Ingebrigtsen
2003-10-17 21:40             ` Simon Josefsson
2003-10-17 21:53               ` Lars Magne Ingebrigtsen
2003-10-17 22:05                 ` Simon Josefsson
2003-10-17 22:42                   ` Lars Magne Ingebrigtsen
2003-10-18  0:06                     ` Simon Josefsson
2003-10-18  0:43                       ` Lars Magne Ingebrigtsen
2003-10-18  1:00                         ` Simon Josefsson
2003-10-18  1:10                           ` Lars Magne Ingebrigtsen
2003-10-18  1:39                             ` Simon Josefsson
2003-10-18  1:45                               ` Lars Magne Ingebrigtsen
2003-10-18  1:52                                 ` Simon Josefsson
2003-10-18  2:00                                   ` Simon Josefsson
2003-10-18 13:55                                     ` Lars Magne Ingebrigtsen
2003-10-18 15:17                                       ` Simon Josefsson
2003-10-18 15:24                                         ` Lars Magne Ingebrigtsen
2003-10-18 23:14                                           ` Simon Josefsson
2003-10-19 11:22                                             ` Lars Magne Ingebrigtsen
2003-10-18  9:58                                   ` Romain FRANCOISE [this message]
2003-10-18  2:31                               ` Simon Josefsson

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=877k32q348.fsf@orebokech.com \
    --to=romain@orebokech.com \
    /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).