From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Charset encoding brokenness
Date: Tue, 28 Oct 2003 04:01:22 +0100 [thread overview]
Message-ID: <m38yn63w1p.fsf@defun.localdomain> (raw)
In-Reply-To: <m33cdeb0jn.fsf@defun.localdomain> (Jesper Harder's message of "Tue, 28 Oct 2003 02:42:20 +0100")
Jesper Harder <harder@ifa.au.dk> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Jesper Harder <harder@ifa.au.dk> writes:
>>
>>> Charset encoding is currently broken in quite a few places, viz.
>>>
>>> · Forwarding. `C-u N C-c C-f' for N=1,2,4 is broken if the CTE of
>>> the forwarded message is 8bit.
>>>
>>> · Digesting. `S o p' and `S o m' is similarly broken if
>>> `message-forward-as-mime' is nil.
>>
>> Did my C-c C-f rewrite cause this?
>
> N=1 appears to work in a Gnus from 2003-07-31, so it probably broke
> that.
Right. Before the rewrite N=1 used `mime-to-mml' -- it doesn't now,
which explains why it's broken.
So the question is: how to forward/digest/etc correctly without
converting to mml?
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.
2. `mime-to-mml' assumes that the message is actually valid MIME.
3. It's broken for pgp/mime.
The last problem could probably be fixed by some special-casing. But
the other two remain.
next prev parent reply other threads:[~2003-10-28 3:01 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 [this message]
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
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=m38yn63w1p.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).