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

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

Re: Character shown as \377 in *Shell* on w32


From: Kenichi Handa
Subject: Re: Character shown as \377 in *Shell* on w32
Date: Thu, 28 Dec 2006 21:39:18 +0900
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.92 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

In article <address@hidden>, "Lennart Borgman (gmail)" <address@hidden> writes:

> >
> > It seems you have set your thousands separator to be a non-breaking 
> > space, and cmd.exe is using cp850 or cp437 for its output, while Emacs 
> > is expecting windows-1252 or iso8859-1.
> >

> I am not sure, but the non-breaking space is then probably coming from 
> Control Panel - Regional and Language Options - Regional Options (tab) - 
> Standard and Formats - Number (on Windows XP). I can think of nothing 
> else I have changed in this area.

> Then this is the normal condition for many pc:s in Sweden. Where do I 
> found the codepage used by cmd.exe? What should Emacs do in this situation?

It seems that default-process-coding-system is not setup
properly on Windows.  When I run Emacs on my Windows,
default-buffer-file-coding-system is set correctly to:
  japanese-shift-jis-dos
but default-process-coding-system is:
  (undecided-dos . undecided-unix)

On the other hand, when I run Emacs on GNU-Linux with
ja_JP.EUC-JP locale, default-process-coding-system is:
  (japanese-iso-8bit . japanese-iso-8bit)

Is this because of DOS/Windows specific code in mule-cmds.el?

---
Kenichi Handa
address@hidden




reply via email to

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