Re: [Nmh-workers] things to mention in 1.3 release announcement?
I think it would be a good idea to mention the change in the default configuration to allow all supported form of masquerading. David Peter writes: > I was looking back through the ChangeLog to see if there was anything in > 1.3 that's particularly worth mentioning in the release announcement. It > looks to me as if it's essentially all bugfixing; but does anybody have > anything they'd like mentioned? __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ Nmh-workers mailing list Nmh-workers@nongnu.org http://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] things to mention in 1.3 release announcement?
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 >encodings. My impression from the changelog was that that was in 1.2 -- 2005-02-23 Oliver Kiddle <[EMAIL PROTECTED]> * 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? -- PMM ___ Nmh-workers mailing list Nmh-workers@nongnu.org http://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] things to mention in 1.3 release announcement?
[EMAIL PROTECTED] wrote: > I was looking back through the ChangeLog to see if there was anything in > 1.3 that's particularly worth mentioning in the release announcement. It > looks to me as if it's essentially all bugfixing; but does anybody have > anything they'd like mentioned? 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 encodings. Oliver ___ Nmh-workers mailing list Nmh-workers@nongnu.org http://lists.nongnu.org/mailman/listinfo/nmh-workers
[Nmh-workers] things to mention in 1.3 release announcement?
I was looking back through the ChangeLog to see if there was anything in 1.3 that's particularly worth mentioning in the release announcement. It looks to me as if it's essentially all bugfixing; but does anybody have anything they'd like mentioned? -- PMM ___ Nmh-workers mailing list Nmh-workers@nongnu.org http://lists.nongnu.org/mailman/listinfo/nmh-workers
