Re: Aging Dependencies?

[email protected]
Newsgroups gmane.mail.exmh.user
Message-ID <[email protected]>
On Wed, 18 Apr 2012 10:22:41 -0400, Ken Hornstein said:
> What I guess happened THERE is something assumed that the characters
> in question were ISO-8859 and converted them to UTF-8.  But since
> exmh thought that the text was in us-ascii, it ended up simply
> displaying the bytes using a "us-ascii" font and that had the
> practical effect of showing the UTF-8 bytes as ISO-8859.  (The UTF-8
> encoding of U+00E4, “ä”, is 0xc3 0xa4, which ends up being displayed
> as U+00C3, “Ô, and U+00A4, “¤â€).  In theory those probably should
> have been displayed as U+FFFD, “�”, but I'm not sure who exactly
> should take care of that.

It's actually more complicated than that - it gets tied into the way exmh
chooses 'faces' and fonts, and is handled differently for scan output and
the message display.  One corner case in particular is in msgShow.tcl, if
m_tagnames specifies a highlighting for a header line that includes a font
that doesn't match the encoding (for instance, specifying that From:
is blue with a particular iso8859-1 font, but the header included a
=?utf-8?q?whatever field), you end up with good and proper mojibake.
I believe the scan window has the same issue if *Ftoc*Text.font isn't
the same encoding as the output of nmh 'scan'.

It would be easy enough to fix, if I had a clue what the correct fix is. The
problem is exacerbated by the fact that the font appears to be set before we
have handled any rfc2047 encoding.

So what do people think it should do? I'm open to suggestions...

_______________________________________________
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

iQIVAwUBT47yegdmEQWDXROgAQK3vhAAsYRE6JN6408CJz5br8rglCQopF9IQ/EM
puVX2NHQ41djWXxNOmn2eWXIqcND+x6Fb977ClgGsEAa1iZsCVZxG5KgSWyzrYFl
drCt3BXLblEMMy4S2yLJSui84PaKj1N55ZKR+SRM5byjP5bcOmMHO1NC6HZ40XPV
+OU3ocT/btRWFVevbuFGIRg4pZJTAcUpb2ov2m46N4DHAVZBdVL+AKD+d4DUV6Hy
RYFLGOccrEeY01LFaOa8tG1kRMMc8F4rjgZSjvYKS54n7ockvQyk2M+XZaOVkCeW
c16o7iPZLR668OVl09VxocohBrm5UdVUjkpOQ9wvRy3LryHU7lvn/kJgZdbC91cL
P9E7ZIc300D2QJ5EJbVRgMjCzo2kk4IoPyEBQuj4Nc/sy4WcRzJww/gN/ey7UpqC
/tGDWoc7wIfzIisRheDeyVwiW79ZfHxP6Vun6HXsaxGGJjpPOby23FzgLFsauHTD
Sh9JnPM1oFAyvV9MHOBt1fdtxe41o6aAkQVrGhn6wYFZv8IyedMd8/H5ZeGwT6Ia
nMqE5dpKXYFA9+dvk0vfspEi82+PY/NhG7Dl40cKJ2Es57M7JLaqRnRDPKGw398n
INZsVfiIVUVVRGnVcqh/YM/InUJa+FV/TQRplMQdrsuBLMyuyOlXnfawunr+wCv+
AzAmkn8PjqI=
=Z6Fs
-----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.