On Sun, Apr 21, 2019 at 02:35:06PM -0600, Paul Gilmartin wrote:
Is this the right place for bug reports, or should I go via <https://gitlab.com/muttmua/mutt/issues>?
This mailing list is always a good place to start. If you then become convinced it's a bug in Mutt, report the issue on gitlab.
I have a file which I believe is ISO8859-5. I would like to attach it with charset=ISO8859-5. When I enter with ^T charset=Iso8858-5, I'm queried, "Convert to Iso8859-5 upon sending? ([yes]/no):". Answering "y" or "n" seems to have no different effect.
Answering "y" means you believe the file is currently in the native system charset and you want Mutt to convert it to iso8859-5 before sending it.
Answering "n" means you believe the file is *already* in iso8859-5 and that Mutt should not touch the file but just label it as iso8859-5.
Should the difference between "Iso8859-5" and "iso-8859-5" matter?
I'm not a charset expert, so I don't know for sure. I believe 'iso-5589-5' is technically more correct and would be better.
It appears then, to MacOS Mail.app, in my AOL IMAP Sent folder with MIME headers:
What appears in your Sent folder is what Mutt put on the wire, so if that's correct then most likely this is not a Mutt issue. Perhaps you should try again with 'iso-5589-5' and see if it helps.
-- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
