On Tue, Feb 16, 2016 at 02:26:11PM +0100, Ionel Mugurel Ciobîcă wrote: > If you use an unicode aware terminal (for example uxterm instead of > xterm (to take care of fonts))
FWIW, xterm is perfectly aware of UTF-8, though it respects your locale and needs to be configured to use a unicode font, such as the gnu universal font, in order to display most Unicode glyphs. It may (or may not) be simpler to make uxterm display the characters you expect to see, though if you get it working with xterm, it's more or less assured it will work with every other application with no additional configuration. > and then set your locale to en_IE.UTF-8 > instead of en_IE.ISO8859-15, and tell also mutt about what locale are > you using, then you are set to see all the characters you receive... DO NOT EVER explicitly tell mutt (via its config) what your locale is unless you are an expert and know exactly why you are doing this. Setting your locale properly at the system (or shell) level is the only thing you need to do to make mutt handle your local encoding properly. Explicitly setting an encoding in mutt's config is only asking for trouble. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
pgp27xRB8M2yT.pgp
Description: PGP signature
