Re: shell-quote-argument and multibyte

[Kenichi Handa <handa@m17n.org>]

In article <m3smsmm4ye.fsf@cicero.benny.turtle-trading.net>, Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de> writes:
> Hi Lars,
> Lars Hansen <larsh@math.ku.dk> writes:
>>  I dired one can specify a list of external viewers. This is a nice
>>  new feature. However, there is a problem, at least on Windows, when
>>  there are special characters in the file name. I don't know where
>>  the problem should be fixed, but I do know that it disapears if
>>  string-make-unibyte is called on ARGUMENT in shell-quote-argument.

By default, process arguements (including the filename in
the above case) are encoded by:
    (cdr default-process-coding-system)
And usually, it is the same as
default-file-name-coding-system.

So, if it doesn't work, it means that something is wrong in
setting up coding systems on Windows.

Please show me the result of C-h C RET.

Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de> writes:

> I would guess you rather want something like this to be generic:
>   (decode-coding-string ARGUMENT
>                         (or file-name-coding-system
>                             default-file-name-coding-system))

No.  At least "decode" must be actually "encode".  And, it
shouldn't be done in shell-quote-argument.  Such an encoding
should be done only for file names.

---
Ken'ichi HANDA
handa@m17n.org