Simon Fondrie-Teitler dixit:
Eduardo Chappa cha...@gmx.com writes:
I am also concerned that you are patching pith/mailview.c. Why is that the
case? Why is it necessary now and was not necessary before?
Thorsten, could you comment on why the patch touches pith/mailview? I
The patch says:
#
On Sun, 25 May 2014, Thorsten Glaser wrote:
Sure: When you view a raw message using ‘h’, and the message was base64
content-transfer-encoded, you do *not* want this base64 to be
interpreted as if it were in the content-type/charset, because the
charset only applies to the message *after*
Eduardo Chappa dixit:
But the h command does not do that, that is, you should be able to see
I should, right, but the UTF-16 eMail shows that this is only a should,
not an “is”. But since the other charsets are all supersets of ASCII,
this is never noticed otherwise. I think with an eMail in
On Sun, 25 May 2014, Thorsten Glaser wrote:
But the h command does not do that, that is, you should be able to
see
I should, right, but the UTF-16 eMail shows that this is only a should,
not an “is”. But since the other charsets are all supersets of ASCII,
this is never noticed otherwise. I
Eduardo Chappa dixit:
binary), the normal body (the one which people normally write) is normally
encoded in quoted-printable. Why is anyone sending base64 to encode the main
No, using base64 there is perfectly reasonable, especially if you
are Asian and use UTF-8 encoding (much shorter), or
On Sun, 25 May 2014, Thorsten Glaser wrote:
No, using base64 there is perfectly reasonable, especially if you are
Asian and use UTF-8 encoding (much shorter), or use UTF-16 (the sheer
amount of NUL bytes is crazy even with ASCII), or if the eMail is
auto-generated and the script doing it went
Eduardo Chappa cha...@gmx.com writes:
I am also concerned that you are patching pith/mailview.c. Why is that the
case? Why is it necessary now and was not necessary before?
Thorsten, could you comment on why the patch touches pith/mailview? I
don't completely understand what Eduardo means that
On Sun, 18 May 2014, Simon Fondrie-Teitler wrote:
I've tested the attached patch, and was able to apply it to the alpine
Debian package. I was also able to successfully apply the patches the
debdiff put into debian/patches/ to the alpha version of alpine. I've
attached both for convenience.
I've tested the attached patch, and was able to apply it to the alpine
Debian package. I was also able to successfully apply the patches the
debdiff put into debian/patches/ to the alpha version of alpine. I've
attached both for convenience.
Eduardo, are you willing to apply this upstream, and
Package: alpine
Version: 2.10+dfsg-1.1
Severity: normal
Tags: patch
Hi,
attached debdiff contains:
• a new patch adding MIME compliant (RFC2781 §4.3) handling of
UTF-16, UCS-2 and UCS-4 encoded messages (check for LE BOM,
use BE if none found), adds {UTF-16,UCS-{2,4}}{L,B}E charsets
that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thorsten Glaser t...@mirbsd.de schrieb:
and triggered by Natureshadowbissues in an unnamed concurrent product.
For the record, I have absolutely no idea what tg is talking about, but I'll
keep clarifying that off the BTS ;).
-BEGIN PGP
11 matches
Mail list logo
