Is this the right place for bug reports, or should I go via
<https://gitlab.com/muttmua/mutt/issues>?
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. After I reply "n", I see:
"Character set changed to Iso8859-5; not converting."
Then:
"I 2 /tmp/....txt [text/plain, 8bit, iso-8859-5, 1.3K]
Should the difference between "Iso8859-5" and "iso-8859-5" matter?
It appears then, to MacOS Mail.app, in my AOL IMAP Sent folder with MIME
headers:
--4SFOXa2GPu3tIq4H
Content-Type: text/plain; charset=Iso8859-5
Content-Disposition: inline; filename="ISO8859-5.txt"
Content-Transfer-Encoding: 8bit
... and the content correctly shows Cyrillic characters.
0 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
0 10 20 30 40 50 60 70 80 90 a0 b0 c0 d0 e0 f0
0 0 & - Њ ц й я ь { } \ 0
1 1 љ / Ћ a j ~ ы A J 1
2 2 ђ њ Ѓ Ќ b k s з B K S 2
But in my Inbox, with similar MIME headers:
--4SFOXa2GPu3tIq4H
Content-Type: text/plain; charset=Iso8859-5
Content-Disposition: inline; filename="ISO8859-5.txt"
Content-Transfer-Encoding: 8bit
...
and the content is definitely not Cyrillic:
0 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
0 10 20 30 40 50 60 70 80 90 a0 b0 c0 d0 e0 f0
0 0 & - � � � � � { } \ 0
1 1 � � / � a j ~ � A J 1
2 2 � � � � b k s � B K S 2
3 3 � � � � c l t � C L T 3
Should I just blame AOL? Outbound or inbound? Is there a way to bypass the
problem?
Thanks,
gil
