Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Charset encoding brokenness
Date: Tue, 28 Oct 2003 17:41:35 +0100	[thread overview]
Message-ID: <m3d6chz54w.fsf@defun.localdomain> (raw)
In-Reply-To: <87ism9rgax.fsf@unix.home> (Vasily Korytov's message of "Tue, 28 Oct 2003 10:07:34 +0300")

deskpot@despammed.com (Vasily Korytov) writes:

> On Tue, 28 Oct 2003 04:01:22 +0100, Jesper Harder wrote:
>
>> I think `mime-to-mml' is the wrong thing for most purposes for a
>> variety of reasons:
>>
>> 1. When I ask someone to forward a message, I usually want a
>> _verbatim_ copy, not an interpretation by Gnus.
>
> Hm. Then we really should have different options to have both
> interpretation and verbatim plaintext forwards.

We already have that ... the problem is that verbatim forward is
currently broken.

> In fact, the interpretation is much more often desired. What the use do
> I have of base64 undecoded?

If you just want to read the message, then it doesn't matter if it's
base64 encoded -- Gnus decodes it automatically, so you won't even
notice unless you view the raw message.

> 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.




  reply	other threads:[~2003-10-28 16:41 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 [this message]
2003-10-29  7:03           ` Vasily Korytov
2003-10-29 12:39             ` Vasily Korytov
2003-10-29 21:22             ` Simon Josefsson
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=m3d6chz54w.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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).