Oliver Kiddle wrote:
My change to better support different character encodings is definitely
worth mentioning. It now uses iconv to convert headers when doing scan.
There is also some initial support for multi-byte character encodings:
field widths in scan listings account for the actual width of a string
(if the string came from the e-mail as opposed to the format file). The
-width option to scan still does not support multibyte character
My impression from the changelog was that that was in 1.2 --
2005-02-23 Oliver Kiddle <okiddle(_at_)yahoo(_dot_)co(_dot_)uk>
* use iconv to convert RFC-2047 encoded headers to the
character set used by the current locale
and the 1.2 release was 2005-12-15.
Is that wrong?
Nmh-workers mailing list