> I've just added windows-1252 in `coding-priority' info of
> "Laint-1" and "German" language environment.
I'm not sure this is right, because windows-1252 covers basically all bytes,
so there's no way to find out that a file is not in windows-1252. It's not
terrible, but it means that this change is not completely harmless.
Now, given the fact that this problem is rare I'm not sure it's worth
the risk.
A better solution is a new command which would
try to explain to the user why what he sees is not what he expected.
I.e. the user could point to a \NNN char and do M-x explain-decoding-error,
and then get an explanation like "this byte-sequence here prevented the use
of utf-8, that byte-sequence there prevented the use of latin-1, ...".
And she could even say C-u <somechar> M-x find-coding-system, and Emacs
could try and figure out which coding-system to use such that the \NNN gets
properly decoded into <somechar>.
Stefan
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
