Eli Zaretskii wrote:
Date: Sun, 18 Feb 2007 23:48:29 +0100
From: "Lennart Borgman (gmail)" <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], [email protected]
Eli Zaretskii wrote:
Date: Sun, 18 Feb 2007 23:32:01 +0100
From: "Lennart Borgman (gmail)" <[EMAIL PROTECTED]>
CC: Eli Zaretskii <[EMAIL PROTECTED]>, [email protected]
I wonder if this has something to do with the mime codes? I do not know
anything about it, but could it be that the web server changes something
in the output?
I think the problem is simply that IE, like Emacs, needs to be told
the encoding explicitly, when its defaults are wrong. There's no
magic wand here.
Maybe, I just do not understand why IE6 just does not save the
bytestream it recieves.
For the same reason Emacs doesn't do that with non-ASCII text: it
doesn't treat it as a byte stream, it treats it as an encoded text.
Yes, and I guess they do that for a reason, see below. If I understand
things correctly here this thread was mostly about downloading an elisp
file.
It looks to me like if you are trying to save what the web browser shows
then it will save something it can show again, not the original
downloaded file. When the web browser downloads the file it usually has
some extra information from the mime headers. That information helps it
display the file. My guess is that when the web browser saves the file
that is displayed it tries to merge that information with the downloaded
file. Therefore the file changed in this way is different from the
downloaded file.
So instead of saving what is viewed in the browser the user need to
download the file directly to his disk. There use to be something like
"right click and choose Save Link As" or something similar in the web
browsers for this.
Would it suffice to tell the users how to download the files?
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
