UTF-8 is one of the charsets supported by iconv but the patch translates beween any pairs supported by iconv, so you can have your display terminal configured for the encoding you want and let the patch use iconv() to convert all mail to this encoding.

The patch also introduces a pine config setting called send-charset which allows pine users to set a charset to which all composed, forwarded and replyed mail should be converted to, independent of which terminal charset you use at the moment. This feature has been disabled in the patch in version 4.61 and 4.64.

Configuration:

• It's not needed to do anything. If you do nothing, pine will just work as usual, the only thing you'll notice that you'll see mails encoded in character sets which are not supported by standard pine(such as UTF-8) should be handled properly now, provided that the characters in the mails you receive have an represenation in the character set you use so that they can be converted.

  If it's not possible to convert characters, the hex codes are displayed in hexadecimal coding like this: [e9][fg]. The behavior in version 4.64 is different, though, you will see question marks instead.

Notes for users who want to configure UTF-8 as terminal charset:

• Recent Linux Distributions, will use an locale UTF-8 by default, if it does not, you get an xterm which UTF-8 support by entering in X:

  	LANG=en_US.UTF-8 xterm

Compilation: