Dixi quod…
>I don’t know if it is something in the encoding of the
>eMail or a bug in alpine’s interpretation thereof.
It’s apparently something in how alpine creates the eMail.
For example, this mail from the BTS contains:
--===============0580578218==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: attachment; filename="mksh-assockit.txt"
Content-Transfer-Encoding: quoted-printable
Which is legible in alpine (I even get unbroken lines with
the boxed headline text).
Alpine itself creates these attachment subheaders:
--447507459-1012153757-1366993344=:9804
Content-Type: TEXT/plain; name=mksh-assockit.txt
Content-Transfer-Encoding: BASE64
Content-ID: <alpine.deb.2.02.1304261822230.9...@tglase.lan.tarent.de>
Content-Description:
Content-Disposition: attachment; filename=mksh-assockit.txt
It’s missing a charset and possibly assuming ISO_646.irv:1991 then
(and, thus (probably correctly) truncating to 7bit)?
On the other hand: alpine couldn’t know that the attached file is
indeed a UTF-8 file, so personally I think not adding a charset is
correct. It should though not corrupt the attachment upon saving,
and, maybe, when displaying, assume it’s in the correct, local, or
global message charset (which is UTF-8 in this case), or offer an
encoding choice menu similar to what GUI MUAs do.
I guess forwarding this to upstream sounds reasonable, thus.
bye,
//mirabilos
--
> emacs als auch vi zum Kotzen finde (joe rules) und pine für den einzig
> bedienbaren textmode-mailclient halte (und ich hab sie alle ausprobiert). ;)
Hallooooo, ich bin der Holger ("Hallo Holger!"), und ich bin ebenfalls
... pine-User, und das auch noch gewohnheitsmäßig ("Oooooooohhh"). [aus dasr]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
