[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
mhfixmsg: possible bugette, -textcharset/-replacetextplain questions
|
From: |
Conrad Hughes |
|
Subject: |
mhfixmsg: possible bugette, -textcharset/-replacetextplain questions |
|
Date: |
Wed, 25 Dec 2019 22:36:40 +0000 |
A few questions re: mhfixmsg (nmh 1.7.1-4 on Debian)..
- I'm contemplating running the above command on my entire email
archive; is there any reason not to use "-textcharset utf-8" on
everything? Seems to me like an eminently sensible thing to do on
the face of it, as without it trying to read emails containing
(heaven forfend) mixed encodings is asking for trouble. Think
that's been mentioned here before as a source of headaches.
- Similarly I was wondering about adding -replacetextplain to all
conversions, but I'm kindof thinking that that's not so smart, nor
so useful — since simply running mhfixmsg will render stuff usefully
grep'able, the UTF-8 conversion will make the files more reliably
readable, and 'show' will prefer HTML parts anyway so the
replacetextplain doesn't really give me anything useful. Is that
right?
- The attached message contains some Windows-1252 parts, yet when I
try to "mhfixmsg -textcharset utf-8 -verbose" on it, I get the
following:
mhfixmsg: 1 part 1.2, decode text/plain; charset="Windows-1252"
mhfixmsg: 1 part 1.1, decode text/html; charset="Windows-1252"
mhfixmsg: 1 part 1.2, convert utf-8 to utf-8
mhfixmsg: 1 part 2, convert utf-8 to utf-8
.. "convert utf-8 to utf-8" looks like a reporting bug, no? Should
be "convert Windows-1252 to utf-8"? The conversion from 1252 *is*
actually performed.
Conrad
From: address@hidden
To: address@hidden
Subject: Blah
Date: Tue, 15 May 2018 08:50:13 +0000
Message-ID: <address@hidden>
Content-Type: multipart/mixed; boundary="----------=_1526374215-10656-57"
MIME-Version: 1.0
Content-Transfer-Encoding: binary
This is a multi-part message in MIME format...
------------=_1526374215-10656-57
From: address@hidden
To: address@hidden
Subject: Blah
Date: Tue, 15 May 2018 08:50:13 +0000
Message-ID: <address@hidden>
Content-Type: multipart/alternative;
boundary="_000_VI1PR0501MB2832D910EEB111D8526EDDEEAC930VI1PR0501MB2832_"
MIME-Version: 1.0
--_000_VI1PR0501MB2832D910EEB111D8526EDDEEAC930VI1PR0501MB2832_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Dear All,
'Do join us if you can.=92
--_000_VI1PR0501MB2832D910EEB111D8526EDDEEAC930VI1PR0501MB2832_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40";>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body>
<p>'Do join us if you can.=
=92</p>
</body>
</html>
--_000_VI1PR0501MB2832D910EEB111D8526EDDEEAC930VI1PR0501MB2832_--
------------=_1526374215-10656-57
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Description: dot sig
A dot sig
------------=_1526374215-10656-57--
- mhfixmsg: possible bugette, -textcharset/-replacetextplain questions,
Conrad Hughes <=