Subject: bug#6974: Emacs doesn't like Swedish ä (on w32)

From: Andreas Röhler <[email-masked]>
Date: Fri, 03 Sep 2010 11:46:00 +0200

Am 03.09.2010 11:01, schrieb Eli Zaretskii:
>> Date: Fri, 03 Sep 2010 10:03:32 +0200
>> From: Andreas Röhler<[email-masked]>
>> Cc:
>>
>> seeing the similar:
>>
>> when opening a file containing non-ascii chars, german
>> umlauts for example, in some case these aren't shown
>> as glyphs but as numbers.
>
> This is a different problem entirely, please file a separate bug
> report

done with bug#6941

(although my guess is that this is some cockpit error on your
> part,

a theoretically possible source might be code from some 
auto-saved-buffer-file mangled in (?), even if not noticed that.

  so perhaps discussing this on emacs-devel is a better way of
> resolving it).
>
>> See screenshot attached how the following code looks
>> like:
>>
>> (define-abbrev-table
>>     'global-abbrev-table
>>     '(("Infinity" "∞" nil 0)
>>       ("alpha" "α" nil 2)
>>       ("beta" "β" nil 1)
>>       ("gamma" "γ" nil 1)
>>       ("theta" "θ" nil 0)))
>
> The screenshot shows "t" at the mode-line's left edge, which means
> Emacs decoded the file's contents with raw-text coding-system.
> raw-text interprets all non-ASCII characters as raw bytes, and
> displays them as such, with octal escapes.
>
> The most probable reason for Emacs not to decode the file correctly
> (as UTF-8) is that the file includes some bytes that are invalid UTF-8
> sequences.  What happens if you force UTF-8 with "C-x RET c" before
> visiting the file with "C-x C-f"?
>

All fine at the first glance than.

However, re-opening the newly saved buffer repeats the wrong display.

Also when saving, it always prompts for coding-system, suggests raw-text 
first.

Setting buffer-file-coding-system explicitly to utf-8-unix, followed by 
a save, doesn't change the wrong display after new opening.

Difference so for from earlier, it accepts a save at all.