-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Tuesday, October 5 at 08:58 PM, quoth Matthias Apitz:
>In the output of mutt -v it says (among other stuff):
>
>-HAVE_ICONV
>-ICONV_NONTRANS
Ahhh, there you go.
>but nothing positiv/negativ about UTF-8. I can't check the
>exact configure values (because the port is on my real work
>laptop and on my netbook I only have the created package
>installed). But it is curious, I can send UTF-8 messages
>with this mutt :-)
Right, sorry. Apparently mutt can handle utf-8 natively to some
extent. It's the other character sets that give mutt fits without
having libiconv to do the hard conversion work from any given utf8
character to any other character in whatever character set.
Anyway, the point is: full character set support requires some form of
libiconv. :)
~Kyle
- --
No one really listens to anyone else, and if you try it for a while
you'll see why.
-- Mignon McLaughlin
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iQIcBAEBCAAGBQJMq3uPAAoJECuveozR/AWeZ9AQAIpSj9kZc4mugnxks+eHCcRs
9gnq0Hul7pOgXAfZ4/761MBs+iEGmj2zFdBlzdXfzD9FJzATaoPPLY0pqWw8otDP
TMQ5CY6OJPzeCO8I/NwMeCIPOFZkXqBEbKfadZVtX7yPdCU0Sm2SX/b+F4AntHF8
VsdHOOBW5+zg4A985Ft9wKwlXg2r5c88hVw7MgUs7TJ+gSozvH9smKaWJ1TRq+C2
P3zd7t05EOvAYnYzBOG/u60QxQ+M0rRSN2kF8w8YxvNMx6M9NjOm/M0ezcUbF7ja
yvy5qhwUdhfRUqqhbh3id36gq/bgySmKXsQ8dmcvP9Xd6SfXEd2kwhvYppn+hnnL
S8hpXgv0LRKk+LOqMOrXyIr8ERISZQl8ggKotXxo02VVolRmVWgoPotomy3dMM22
cz6mT+i43CXC+9jgxA0HtUQH8jsDTjF3D7IxMWnWtWUkbCLkfRdD7jYSR/37pKCP
riFj+zbOSvDvKUQd/Y3LoIGcVAf1nuCCMWp14k2ZNHfqEwoqd5AMiBKZ5NZcEq3G
yYkK/jyzxQrEKDbFhH1FdsSEfk2VDSjEUsb4KeSxtAWKztdEAhp4CBsXENLaBisS
HZR0dVBWMvFVd5YYwnsDt9SLiI/51Vfx/cQBOPSWfKMDWwvg9gKnWYRcD1Cjb4L7
dvZFH4t7VkhYJSzwAnsH
=tAD1
-----END PGP SIGNATURE-----
