[Top][All Lists]

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

Re: on eshell's encoding

From: Eli Zaretskii
Subject: Re: on eshell's encoding
Date: Tue, 26 Jul 2016 21:35:27 +0300

> From: Yuri Khan <address@hidden>
> Date: Wed, 27 Jul 2016 00:26:42 +0600
> Cc: "address@hidden" <address@hidden>
> On Wed, Jul 27, 2016 at 12:17 AM, Eli Zaretskii <address@hidden> wrote:
> > The only way to break the limitations of the
> > system codepage is to use the Unicode (a.k.a. "wide") APIs, which
> > expect strings in UTF-16 encoding.  But that is not currently
> > supported in Emacs, due to boring technical problems.
> It’s not even clear if using the wide API on the caller side will
> suffice. The callee also needs to cooperate, by using the
> corresponding wide API to retrieve the command line arguments.

Yes, and that's one of the few reasons why Emacs on Windows doesn't
bother to use the wide APIs: too few programs Emacs users normally
invoke can cooperate like that.  But if Emacs did use the wide APIs,
it wouldn't have been a loss, because programs that use ANSI APIs to
access their command-line arguments would have them converted to the
system codepage by Windows, and so it would have worked or not exactly
as it does or doesn't now.

reply via email to

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