ChangeLog of the UTF-8 and iconv support patch from:
http://www.suse.de/~bk/pine/iconv/

Example charset aliases(recommended):

charset-aliases=iso-8859-12:windows-1250,
        iso-8859-2:windows-1252,
        iso-8859-11:windows-874,
        iso-8859-8-i:iso-8859-8,
        tis-620:windows-874,
        gb2312:gb18030,
        gbk:gb18030,
        euc-cn:gb18030,
        ks_c_5601-1987:x-windows-949,
        5601:x-windows-949

iconv-aliases=x-windows-949:mscp949,
        euc-kr:mscp949

Latest changes:

8m - Jan 23 2004
----------------
- improve word wrapping further: do not wrap in the middle of an latin
  word, but do not try to wrap at spaces if an double wide character
  is processes, these go to the end of the line and wrap the line there.
- remove the remaining places where the html filter tried to wrap and
  leave these places also to the wrap filter for better display.
- in message view, if the subject is not encoded using RFC2047 and
  the message header has a Content-Type: field with a charse tag, this
  charset is used to convert the subject field(not implemented for
  the message index yet)
- use a separate iconv_t for the charset convert filter to prevent
  conflicts with the message header conversion.
- reduce the changes to rfc1522_decode the absolute minimum.

8l - Jan 14 2004
----------------
- documentation for the effects of the new code now in doc/tech-notes*
- backport some fixes and wrap filter improvements from the pine pre-release
- improved wrapping of UTF-8 message text in message view, print and export
- fixed some minor UTF-8 display problems in the message composer
- pico also diplays UTF-8 characters now

Currently Known Bugs:
---------------------

- The message header editor wraps long lines into multible lines
  but the function which does this(FormatLines) does not know where
  it may split the line and where not. This can destroy an UTF-8
  sequence when it wraps and when using the backspace key on the
  second line, this may result in a segmentation fault(crash of pine).

- The ISO-2022-JP charset conversion feature is currently disabled
  For now, same can be achived with the patch by setting:

        character-set=EUC-JP (for Unix, for PC-Pine SHIFT-JIS)
        send-chars=ISO-2022-JP

- You may need to enable the config switch called
  "disable-2022-jp-conversions" if you want to use
  character-set=EUC-JP or ISO-2022-JP
  (just not tested)
