Re: lisp/ChangeLog coding system

[Stefan Monnier]

> > From: Karl Eichwalder <address@hidden>
> > Date: Sun, 28 Apr 2002 05:06:40 +0200
> > 
> > Richard Stallman <address@hidden> writes:
> > 
> > > Michael, if you can figure out precisely how this happened, it might
> > > lead us to a way to make the Mule features more robust.  Many users
> > > might benefit from that.
> > 
> > Probably the known bug.  The problem is that Emacs sometimes proposes
> > to use a "save" encoding to save a buffer; if the user follows Emacs'
> > proposal file corruption starts.
> 
> If you can show examples of such corruption, please do.  I'm not aware
> of any corruption due to encodings Emacs suggests, although it's true
> that the result might surprise sometimes, especially if the user
> doesn't know what she is doing.

He might be referring to the fact that saving a file with encoding
foo when the first line says "-*- coding: bar -*-" will lead to
corruption.
And more generally if the auto-detection of the coding-system does not
agree with the coding-system used when saving the file.

But of the course the first question (the one RMS asked IIUC) is why
did Emacs not use iso-2202 despite the -*- coding: -*- tag.


        Stefan