all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Karl Eichwalder <keichwa@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: cvs-quickdir and UTF-8 encoded file names
Date: Thu, 21 Aug 2003 06:47:35 +0200	[thread overview]
Message-ID: <shu18bty54.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <200308210136.KAA06356@etlken.m17n.org> (Kenichi Handa's message of "Thu, 21 Aug 2003 10:36:51 +0900 (JST)")

Kenichi Handa <handa@m17n.org> writes:

> Please show me the result of C-h C RET and the values of
> these variables:
>     default-enable-multibyte-characters
>     enable-multibyte-characters
>     default-file-name-coding-system
>     file-name-coding-system

Thanks for asking:

Coding system for saving this buffer:
  Not set locally, use the default.
Default coding system (for new files):
  u -- mule-utf-8 (alias: utf-8)

Coding system for keyboard input:
  nil
Coding system for terminal output:
  u -- mule-utf-8 (alias: utf-8)

Defaults for subprocess I/O:
  decoding: u -- mule-utf-8 (alias: utf-8)

  encoding: u -- mule-utf-8 (alias: utf-8)


Priority order for recognizing coding systems when reading files:
  1. mule-utf-8 (alias: utf-8)
  2. iso-latin-1 (alias: iso-8859-1 latin-1)
  3. mule-utf-16be-with-signature (alias: utf-16be-with-signature mule-utf-16-be utf-16-be)
  4. mule-utf-16le-with-signature (alias: utf-16le-with-signature mule-utf-16-le utf-16-le)
  5. iso-2022-jp (alias: junet)
  6. iso-2022-7bit 
  7. iso-2022-7bit-lock (alias: iso-2022-int-1)
  8. iso-2022-8bit-ss2 
  9. emacs-mule 
  10. raw-text 
  11. japanese-shift-jis (alias: shift_jis sjis)
  12. chinese-big5 (alias: big5 cn-big5)
  13. no-conversion 

  Other coding systems cannot be distinguished automatically
  from these, and therefore cannot be recognized automatically
  with the present coding system priorities.

  The following are decoded correctly but recognized as iso-2022-7bit-lock:
    iso-2022-7bit-ss2 iso-2022-7bit-lock-ss2 iso-2022-cn iso-2022-cn-ext
    iso-2022-jp-2 iso-2022-kr

Particular coding systems specified for certain file names:

  OPERATION	TARGET PATTERN		CODING SYSTEM(s)
  ---------	--------------		----------------
  File I/O	"ChangeLog"		(utf-8 . utf-8)
		"\\.g?z\\(~\\|\\.~[0-9]+~\\)?\\'"
					(no-conversion . no-conversion)
		"\\.tgz\\'"		(no-conversion . no-conversion)
		"\\.bz2\\'"		(no-conversion . no-conversion)
		"\\.Z\\(~\\|\\.~[0-9]+~\\)?\\'"
					(no-conversion . no-conversion)
		"\\.elc\\'"		(emacs-mule . emacs-mule)
		"\\.utf\\(-8\\)?\\'"	utf-8
		"\\(\\`\\|/\\)loaddefs.el\\'"
					(raw-text . raw-text-unix)
		"\\.tar\\'"		(no-conversion . no-conversion)
		"\\.po[tx]?\\'\\|\\.po\\."
					po-find-file-coding-system
		""			(undecided)
  Process I/O	nothing specified
  Network I/O	nothing specified

default-enable-multibyte-characters's value is t

enable-multibyte-characters's value is t
Local in buffer *cvs*; global value is t

default-file-name-coding-system's value is mule-utf-8
file-name-coding-system's value is nil

> And, when you read CVS/Entries directly, how those file
> names are decoded?

Is this the value you want to know?

Coding system for saving this buffer:
  t -- raw-text-unix

To see this value I did:

C-x C-f CVS/Entries RET
M-x describe-coding-system RET

Thanks for your help.

-- 
                                                         |      ,__o
http://www.gnu.franken.de/ke/                            |    _-\_<,
ke@suse.de (work) / keichwa@gmx.net (home)               |   (*)/'(*)

  reply	other threads:[~2003-08-21  4:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-16 16:33 cvs-quickdir and UTF-8 encoded file names Karl Eichwalder
2003-08-21  1:36 ` Kenichi Handa
2003-08-21  4:47   ` Karl Eichwalder [this message]
2003-08-21  6:26     ` Kenichi Handa
     [not found]       ` <shada37yfp.fsf@tux.gnu.franken.de>
2003-08-25  1:14         ` Kenichi Handa
2003-08-25  4:16           ` Karl Eichwalder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=shu18bty54.fsf@tux.gnu.franken.de \
    --to=keichwa@gmx.net \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.