Re: Aging Dependencies?

[email protected]
Newsgroups gmane.mail.exmh.user
Message-ID <[email protected]>
On Wed, 18 Apr 2012 18:13:04 -0400, Ken Hornstein said:

> Yeah, but I'm still trying to figure out what turned a particular single-byte
> ISO-8859 character character into a 2-byte UTF-8 sequence.  It wasn't
> nmh; was it Tcl?

I'm pretty sure it's Tcl code inside exmh, probably in mime.tcl  though I admit
not fully understanding yet how it went astray.

> In the case you describe below, it seems like people should be "encouraged"
> to use a Unicode font and convert those headers to UTF-8 internally
> irregardless of the user's locale.

It's certainly tempting to make the code "encourage" it :)

The biggest problem is that I run Fedora Rawhide on the laptop where I
use exmh and as a result, I've usually got recent versions of everything.
But I'm sure we have exmh users on userspace old enough that their
utf-8 support is a tad lacking.

> Speaking of mojibake ... the part of the message where you quoted
> me was interesting.  The character set was iso-8859-1, the encoding
> was quoted-printable.  Unicode codepoints in my message that are
> valid in ISO-8859 such as U+00E4 were properly encoded using
> quoted-printable.  But Unicode codepoints that were NOT valid in
> iso-8859-1 (U+201C, U+201D, U+FFFD) were simply spit out as UTF-8
> bytes and NOT encoded properly via quoted-printable (which as I
> read it is a violation of RFC 2045).  I don't know if that's how
> the email left your SMTP server..

Well, the GPG signature was still valid, so it must have been already dorked
when it left my laptop. ;)

_______________________________________________
Exmh-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-users
signature.asc (application/pgp-signature, 865 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iQIVAwUBT49ktwdmEQWDXROgAQKrFQ//XwtoSZJCa77tqQsnNLbT92IIRZuY8JIc
cJw7ICDPWwG+gHXRUdopJDAIh7MQFuQPvucSSQxtGAq2/0U2oKmNUH+yYn+J86+6
KPbj0U+G4NQj6pVKgVH1Pik7co73ZRdDCDjw+Q0MvVf/uS3fca40YvjCpKDjw+MK
3xlNdDtb44mnp7U1bFXDv5fy/1dxYFOF6cdWyBWUbg6Ahxjsi53UWBAn++RDRhNh
3/syMWaoPn+ia4cs5HsCw9TDkJNV1FI0DdUbgh/wjiGmNFSmrZ0ERK6k896u8Qw6
hSoEs0m6hEDvi1OeOjfmL38AOBts4kEQ9J6iD+yPQLcS9MG6JB8rI077fBgwU8AE
prrwnHstx26MuC/fUJVMrsrpo9k87NT4s2cSrUUN8eAX7ZJ36pARPSClbDNdtpHn
ohvaut7SRzOdAL5v9hWJ0kdeWBZK2FwgZDAC3n37KGIqKk5o7xYkcx10uXqQdcvD
Xk6ZMon8H1ubjXmCTAVRypxCQzHlo0qme0TvwLt1/BwAFk0bRV9688jd2feIxwOb
QxWMEwxJUl86UIKQIxSbmGKd64mjwSRZXz75TNeFfWgStSrSStdCsqBEFKhK8kvt
JZk/mCBWz1nEloE8vR9OESZX50vX9C7Tg+gr6nPzv9wGtACvFO9gPDdJP1MfN56S
kFivFrQ97AM=
=ZG0C
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.