Gnus development mailing list
 help / color / mirror / Atom feed
From: Carey Evans <c.evans@clear.net.nz>
Subject: More on forwarding quoted-printable encoded messages
Date: 05 Feb 2000 23:11:49 +1300	[thread overview]
Message-ID: <87d7qc557e.fsf@psyche.evansnet> (raw)

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

I've been looking into my problems with forwarding messages some more,
and I believe I've found two separate bugs in Gnus.  If you're not
convinced, could you let me know what else you'd like to me to look
into?

I'm including my original message below.  This time I edited and
resent it as an 8bit encoded message.  If this works the same sending
to the Gnus mailing list as it did to myself, the attached message
will look fine.

Bug 1:  If I press C-d on this message and view the attachment, the
special characters "=" and "ê" show up as their quoted-printable
equivalents, even though the attachment looks fine as I compose the
message, and the entire message looks correct.  A variation on this
would be why my original forwarded message looked wrong in the
complete view, but OK given Kai's suggestion to use C-d.

Bug 2:  When viewing a quoted-printable encoded message, forward it
with S o m.  The message in the buffer includes a header line

    Content-Transfer-Encoding: quoted-printable

but the actual data in the message has been decoded.  When Gnus, Lotus
Notes, mutt and probably other mailers (though not the mailing list
archives) receive the message, they decode it for quoted-printable
again, resulting in the error I had.

If I manually edit the message in the *mail* buffer and change the =
to =3D and the ê to =EA, the message is encoded and received properly.




[-- Attachment #2: Type: message/rfc822, Size: 808 bytes --]

Return-path: <carey@paradise.net.nz>
To: carey@psyche.evansnet
Subject: Forwarding quoted-printable encoded messages
From: Carey Evans <c.evans@clear.net.nz>
Date: 23 Jan 2000 18:27:15 +1300
Message-ID: <87wvp1e4ss.fsf@psyche.evansnet>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I've found a problem in Gnus v5.8.3 (with XEmacs 21.1 p8) when
forwarding messages (with S o m) that I've received with
quoted-printable encoded equals sign characters.  In particular, this
was with a URL like the following:

    http://www.invalid/lookup?id=EA123456

That's "? i d equals E A ...".  I'm forwarding this message at the
bottom of this one, which should show the problem.  When I receive
this message, I see the character at 0xea, i.e. "ê".

From: Carey Evans <c.evans@clear.net.nz>
To: carey@psyche.evansnet
Subject: Forwarding quoted-printable encoded messages
Date: 23 Jan 2000 18:27:15 +1300
Message-ID: <87wvp1e4ss.fsf@psyche.evansnet>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2.1: Type: text/plain; charset=3Diso-8859-1, Size: 460 bytes --]

From: Carey Evans <c.evans@clear.net.nz>
To: carey@psyche.evansnet
Subject: Forwarding quoted-printable encoded messages
Date: 23 Jan 2000 18:27:15 +1300
Message-ID: <87wvp1e4ss.fsf@psyche.evansnet>

I've found a problem in Gnus v5.8.3 (with XEmacs 21.1 p8) when
forwarding messages (with S o m) that I've received with
quoted-printable encoded equals sign characters.  In particular, this
was with a URL like the following:

    http://www.invalid/lookup?id=3DEA123456

That's "? i d equals E A ...".  I'm forwarding this message at the
bottom of this one, which should show the problem.  When I receive
this message, I see the character at 0xea, i.e. "=EA".

[-- Attachment #3: Type: text/plain, Size: 163 bytes --]


-- 
	 Carey Evans  http://home.clear.net.nz/pages/c.evans/

	 This message was composed from the finest electrons
	 used by many of the world's greatest writers.

             reply	other threads:[~2000-02-05 10:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-05 10:11 Carey Evans [this message]
2000-04-20 23:25 ` Lars Magne Ingebrigtsen
2000-04-21 13:59   ` Steinar Bang
2000-04-21 18:42     ` Lars Magne Ingebrigtsen
2000-04-21 20:46       ` Steinar Bang
2000-04-22 12:04         ` Lars Magne Ingebrigtsen
2000-04-23 10:58           ` Steinar Bang
2000-04-23 19:08             ` Lars Magne Ingebrigtsen
2000-04-23 19:50               ` Steinar Bang
2000-04-24 14:29                 ` Lars Magne Ingebrigtsen
2000-04-24 18:03                   ` Steinar Bang
2000-04-26  6:23                     ` Steinar Bang
2000-04-26  8:10                       ` Shenghuo ZHU
2000-04-26  8:23                         ` Steinar Bang
2000-04-26 12:39                           ` Bjørn Mork
2000-04-26 13:14                             ` Steinar Bang
2000-04-26 13:47                             ` Shenghuo ZHU
2000-04-26 13:52                               ` Roman Belenov
2000-04-26 14:23                                 ` Shenghuo ZHU
2000-04-26 13:57                               ` Steinar Bang

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=87d7qc557e.fsf@psyche.evansnet \
    --to=c.evans@clear.net.nz \
    /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).