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

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

Inconsistent behaviour after inserting two latin-X files in buffer


From: Simon Josefsson
Subject: Inconsistent behaviour after inserting two latin-X files in buffer
Date: Sun, 05 May 2002 18:02:21 +0200
User-agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.2 (i686-pc-linux-gnu)

In GNU Emacs 21.2.50.3 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2002-05-05 on localhost.localdomain
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  locale-coding-system: nil
  default-enable-multibyte-characters: t

This applies to Emacs 21.2 as well.  The files ~/latin-1 and ~/latin-2
should contain codepoints endemic to those coding systems, I'm
including examples below.

(LANG/LC_* settings as above)

$ emacs -q --no-site-file
C-x RET c latin-1 C-x i ~/latin-1
C-x RET c latin-2 C-x i ~/latin-2
<remove the text inserted by the first C-x i.)
C-x C-s

You are now queried for the coding system to save the buffer as, with
iso-8859-2 as the default.

$ emacs -q --no-site-file
C-x RET c latin-2 C-x i ~/latin-2
C-x RET c latin-1 C-x i ~/latin-1
<remove the text inserted by the first C-x i.)
C-x C-s

The file is immediately saved as latin-1.

The latter behaviour is preferable IMHO, if it is done safely.

Why doesn't emacs treat all latin encodings equally?  It seems to like
latin-1 better above.

~/latin-1:
foo þÆ
~/latin-2
źedana

reply via email to

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