emacs-pretest-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Coding system of file not recognised correctly


From: Kenichi Handa
Subject: Re: Coding system of file not recognised correctly
Date: Wed, 04 Oct 2006 21:11:47 +0900
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

In article <address@hidden>, Peter Dyballa <address@hidden> writes:

> Hello!
> I have a UTF-8 test file, which comes from the Kermit distribution's  
> utf8.txt. Its name is utf8_txt and it starts with this line to force  
> it into UTF-8:

>       ;;; -*- mode: Text; coding: utf-8; -*-

> diff (GNU diffutils) 2.8.1 tells me that the only difference between  
> the original file and my private version is:

>       0a1
> ;;; -*- mode: Text; coding: utf-8; -*-

> When I launch /usr/local/bin/emacs-22.0.50 -Q it opens utf8.txt (when  
> second file) with a mode-line starting with -u, but utf8_txt gets -E  
> upon opening it first. The next file, when it has UTF-8 contents, is  
> opened with -u in mode-line – and when I open utf8_txt now, it at  
> once gets a -u too!

> I can understand that the non-marked utf8.txt gets -E in mode-line  
> when opened for the first time as first file, errare Emacsem est, too  
> (which does indeed happen), but it's hard to accept that the  
> mentioned header line leads to using some Japanese coding system!

> When the first file I open is some ISO Latin or Mac-Roman or NeXT  
> or ... encoding, then the first UTF-8 file I open, no matter whether  
> it has the header line mentioned above or not, has -E in mode-line.

[...]
>    value of $LANG: de_DE.UTF-8
>    locale-coding-system: utf-8

I'm confused with your wording.  What do you mean by "(when
second file)" and "The next file" in the first paragraph.
And, it's quite strange that some file is detected as some
Japanese coding system in you locale.  Please show me all
the files you used in the above test, and show me what you
actually typed (e.g. "C-x C-f SOME_FILE_NAME RET") along
time line.

---
Kenichi Handa
address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]