On Sat, 06 Nov 2010 11:08:52 +0700, Robert Elz said:
Date:Fri, 05 Nov 2010 21:27:33 +
From:Peter Maydell pmayd...@chiark.greenend.org.uk
Message-ID: e1petor-0002hx...@mnementh.archaic.org.uk
| [Aside: 'columns' is
| usually the same as 'characters'
Peter Maydell wrote:
markus schnalke wrote:
during the next weeks I intend to fix the annoying problem of still
encoded message text in quoted replies.
I completely agree. I'll try to make some time to take another
look at this some time this week. (I'm at the Ubuntu Developer
Summit so I'm in a
[2010-11-05 21:27] Peter Maydell pmayd...@chiark.greenend.org.uk
So send should:
* check for non-ASCII characters
* when present: pick an encoding (first usable one from
a user-configurable list like us-ascii,iso-8859-1,utf-8)
* encode body and headers as per MIME, adding MIME
On Fri, Nov 5, 2010 at 4:48 PM, markus schnalke mei...@marmaro.de wrote:
So send should:
* check for non-ASCII characters
* when present: pick an encoding (first usable one from
a user-configurable list like us-ascii,iso-8859-1,utf-8)
* encode body and headers as per MIME, adding MIME
Date:Fri, 05 Nov 2010 21:27:33 +
From:Peter Maydell pmayd...@chiark.greenend.org.uk
Message-ID: e1petor-0002hx...@mnementh.archaic.org.uk
| [Aside: 'columns' is
| usually the same as 'characters' except that some Chinese/Japanese
| characters are two columns
[2010-10-26 19:18] Peter Maydell pmayd...@chiark.greenend.org.uk
markus schnalke wrote:
during the next weeks I intend to fix the annoying problem of still
encoded message text in quoted replies.
That would certainly be a cool thing to have working.
I'm still becoming familiar with the code
[2010-10-31 19:22] Ralph Corderoy ra...@inputplus.co.uk
I was thinking of a scan(1) replacement that would colour-code the
results, if I wanted.
You can do this by piping the output through a highlighter program, or
even by using a customized format file for scan.
To begin with, I'd be
[2010-10-26 21:03] Oliver Kiddle okid...@yahoo.co.uk
markus schnalke wrote:
(1) Showing messages with different charsets requires a line like
mhshow-charset-iso-8859-1: iconv -f iso-8859-1 | %s
in the profile if your terminal is on UTF-8. It might be worth to
include such processing
And then an mhshow(1) that assumes a UTF-8 terminal
and converts headers and body to that for one seamless less(1)
I personally want mhshow to go away. It should all be integrated into show.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
AFAIK this problem is still unsolved. I only found a hack in the FAQ:
Subject: 05.16 How can I convert quoted-printable to 8bit in
quoted text in replies?
From: Jarle F. Greipsland jarle at idt.unit.no
Date: 22 Aug 1995 10:42:07 +0200
wow. below
Hi meillo,
Using nmh though is currently pretty tough. ;-)
Agreed, in this modern world. I persist with it but that's because it's
what I know. I occasionally have flights of fancy about gradually
replacing some of its commands with Python ones. Am I the only one?
The C code base of nmh
markus schnalke wrote:
during the next weeks I intend to fix the annoying problem of still
encoded message text in quoted replies.
That would certainly be a cool thing to have working.
Has anyone of you already worked on this? Has nayone information that
can help me?
You might be interested in
Thus spake markus schnalke:
Hoi nmh workers,
during the next weeks I intend to fix the annoying problem of still
encoded message text in quoted replies. The problem appears when
running
repl -format
on a message with Content-Transfer-Encoding like quoted-printable or
base64.
Let me
13 matches
Mail list logo
