Hi all,
The other day I sent a UTF-8 encoded text via mail file from my iPad to myself.
When I opened the mail in Mutt on my desktop computer and saved the attached
file, I noticed that the non-ASCII characters in the file (e.g., German ö) had
all been replaced with two question marks. Viewing the attachment in Mutt also
shows question marks for the German umlauts.
When I view the attachment via Fastmail's web interface, it doesn't recognize
that the file is UTF-8 encoded and displays it as (I think) iso-8859-1. Looking
at the raw message, the relevant attachment starts with the following header
block:
--Apple-Mail-2--194737957
Content-Disposition: attachment;
filename=No_Morphology.tex
Content-Type: text/plain;
name=No_Morphology.tex
Content-Transfer-Encoding: quoted-printable
I've uploaded the message to http://wwwuser.gwdg.de/~jkremer/mangled-message, if
anyone wants a closer look.[1]
What surprises me here is that there is no mention anywhere that the attached
file is UTF-8 encoded. Shouldn't this be included? Or is this ok, because the
Content-Disposition is "attachment"? If the latter, might it be considered a bug
that Mutt doesn't save the file correctly? After all, the Fastmail web interface
does save it correctly (Emacs recognises it as UTF-8 encoded), even though it
doesn't display it correctly.
Thanks,
Joost
Footnotes:
[1] Note that I've deleted most of the attachment itself from the message, as
it's pretty long and not relevant, but the part that I've retained still
contains a few non-ASCII characters, especially in two \psset commands and in
the \author command.
--
Joost Kremers, PhD
University of Göttingen
Institute for German Philology
Käte-Hamburger-Weg 3
37073 Göttingen, Germany
