Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: Charset encoding brokenness
Date: Wed, 29 Oct 2003 22:22:04 +0100	[thread overview]
Message-ID: <ilubrrzu4cj.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87n0bkfrvf.fsf@unix.home> (Vasily Korytov's message of "Wed, 29 Oct 2003 10:03:00 +0300")

deskpot@despammed.com (Vasily Korytov) writes:

> You didn't get it: I set message-forward-as-mime to nil and press C-c
> C-f and get a block like:

What you want appear to correspond to my 'Forward-What-I-See, ASCII
purist' mode in my other message.  I think it is the second most
important forward mode to support (pure MIME mode being the first).

>>> And if that wasn't me -- but some poor Outlook or even fido users?
>>
>> Outlook has no problem with viewing base64.  I don't know about Fido,
>> but I'd consider any client which doesn't do base64 to be extremely
>> obsolete.
>
> I know no MUA, that handle such constructions properly. Even Gnus.

Gnus does, but I don't think it is relevant whether any MUA support
displaying a forward like that -- when you forward a RFC 822 message
verbatim, it is for debugging, and it should be possible to send
forwards like that.  It shouldn't be the default though.




  parent reply	other threads:[~2003-10-29 21:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 21:49 Jesper Harder
2003-10-28  0:48 ` Simon Josefsson
2003-10-28  1:42   ` Jesper Harder
2003-10-28  3:01     ` Jesper Harder
2003-10-28  7:07       ` Vasily Korytov
2003-10-28 16:41         ` Jesper Harder
2003-10-29  7:03           ` Vasily Korytov
2003-10-29 12:39             ` Vasily Korytov
2003-10-29 21:22             ` Simon Josefsson [this message]
2003-10-29 21:30       ` Simon Josefsson
2003-10-29 21:17     ` Simon Josefsson
2003-10-31 16:29 ` Simon Josefsson
2003-10-31 22:23   ` Jesper Harder

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=ilubrrzu4cj.fsf@latte.josefsson.org \
    --to=jas@extundo.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).