Re: [Peter Dyballa] Re: Coding system of file not recognised correctly

[Peter Dyballa]

Am 07.10.2006 um 18:47 schrieb Chong Yidong:

> Your original bug report is very difficult to read, so let me see if I
> can simplify the recipe.  With the file utf8.txt saved to $HOME, I do
>
> $ echo ";;; -*- mode: Text; coding: utf-8; -*-" > utf8_txt
> $ cat utf8.txt >> utf8_txt
> $ LANG=de_DE.UTF-8 emacs

Right! I did not want to leave Kermit's utf8_txt as is to have  
another test case whether this file, that has no .txt extension, is  
determined as a text file. So I created a sym-link utf8.txt that  
points to utf8_txt in a different directory, and I created utf8_txt  
with a method like above.

> C-x C-f utf8_txt RET     => utf8_txt opened with "u" on modeline.
> C-x C-f utf8.txt         => utf8.txt opened with "u" on modeline.
>
> So everything seems to work for me, at least on GNU/Linux.  If you
> follow this exact procedure, does it fail for you?

For me only the second UTF-8 encoded file had "u" in the mode-line.  
The reason it *had*, is that I had in load-path four ELisp files:

pete 123 /\ ls -l /Library/Application\ Support/Emacs/subst-* Quellen/ 
Emacs_CVS/emacs/lisp/international/subst-*.el
-rw-r--r--   1 root  admin  223828 12 Apr 23:50 /Library/Application  
Support/Emacs/subst-big5.el
-rw-r--r--   1 root  admin  120447 12 Apr 23:49 /Library/Application  
Support/Emacs/subst-gb2312.el
-rw-r--r--   1 root  admin  215877 12 Apr 23:50 /Library/Application  
Support/Emacs/subst-jis.el
-rw-r--r--   1 root  admin  132897 12 Apr 23:48 /Library/Application  
Support/Emacs/subst-ksc.el
-rw-r--r--   1 pete  pete   223828  4 Jul  2005 Quellen/Emacs_CVS/ 
emacs/lisp/international/subst-big5.el
-rw-r--r--   1 pete  pete   120447  4 Jul  2005 Quellen/Emacs_CVS/ 
emacs/lisp/international/subst-gb2312.el
-rw-r--r--   1 pete  pete   215877  4 Jul  2005 Quellen/Emacs_CVS/ 
emacs/lisp/international/subst-jis.el
-rw-r--r--   1 pete  pete   132897  4 Jul  2005 Quellen/Emacs_CVS/ 
emacs/lisp/international/subst-ksc.el

They were needed by some Carbon Emacs that failed to load them from  
its resources. After I removed these four files (reported with their  
full path names in *Messages*) and GNU Emacs loads the compiled  
versions in /usr/local/share/emacs/22.0.50/lisp/international (only  
the files' names without extensions are reported in *Messages*) the  
UTF-8 encoded files load correctly with "u" in mode-line!

Strange, isn't it?

--
Greetings

  Pete

One doesn't expect governments to obey the law because of some higher  
moral development.  One expects them to obey the law because they  
know that if they don't, those who aren't shot will be hanged.
                                                 --Michael Shirley