> From: "Drew Adams" <[EMAIL PROTECTED]>
> Date: Sun, 18 Feb 2007 11:29:57 -0800
> Cc: [email protected]
> >
> > > Does this mean that even when the text gets garbled by those browsers
> > > it will still be decoded correctly when the resulting file is visited
> > > in Emacs?
> >
> > Yes.
> > Stefan
>
> On that, I definitely disagree. My experience proves the contrary. I suppose
> it depends what is meant by "text gets garbled by those browsers". What I
> see is that the characters are themselves changed in the file, and the
> coding tag therefore has no way of recuperating; it cannot know what
> characters were intended originally.
>
> You have only to download the file from
> http://cvs.savannah.gnu.org/viewcvs/emacs/emacs/lisp/ to see what I mean.
> Save it directly to disk and then open it in Emacs (22). I don't know
> whether this represents a browser problem or a Web site problem, however.
Please tell the details about how you downloaded and saved the file to
disk. It is impossible to know what went wrong without these details.
I did it twice with two different methods:
. Clicked the "download" link and saved the file to disk.
. Clicked the "view" link; then, after seeing that the Unicode
characters are displayed incorrectly, clicked View->Encoding from
the menu bar, selected "Unicode UTF-8", which fixed the display;
then File->Save As, selected "Text files" and made sure the
encoding is set to UTF-8; clicked OK.
Both methods gave me a valid UTF-8 encoded file that displayed
correctly in Emacs 22.
> I used the most common browser (still), IE6.
Same here.
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
