emacs-devel
[Top][All Lists]
Advanced

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

Re: Fcall_process: wrong conversion


From: Kenichi Handa
Subject: Re: Fcall_process: wrong conversion
Date: Thu, 18 May 2006 15:26:54 +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>, "Herbert Euler" <address@hidden> writes:

>> > For unifying character encodings?
>> 
>> I don't understand the meaning of "unifying character
>> encodings".

> I meant to make encoding for arguments and file the same.

I see.

>> > I.e. if the file is in japanese-shift-jis, but command argument is in
>> > chinese-gbk, encoding arguments will make sure all characters are in
>> > japanese-shift-jis, won't it?
>> 
>> I don't understand what "if ..." part actually means.  Who
>> makes command argument in chinese-gbk?

> For example, I wrote a lisp command which uses `call-process' and
> contains characters in chinese-gbk as arguments.  I meant, when
> I apply this command to a japanese-shift-jis file, `call-process' will
> encode the chinese-gbk characters to japanese-shift-jis in background,
> won't it?

It's hard to understand what you mean.  What do you mean by
"apply this command to ... file"?  Does it mean that you
give the file name to call-process as INFILE argument?  But,
how does it result in "encode the chinese-gbk characters to
japanese-shift-jis"?  Emacs doesn't detect the encoding of
INFILE.  So how does Emacs know about `japanese-shift-jis'
first of all?

And first of all, CVS Emacs doesn't have chinese-gbk coding
system.  Are you talking about the behavior of
emacs-unicode-2?

---
Kenichi Handa
address@hidden




reply via email to

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