X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-7.9 required=5.0	tests=AWL,BAYES_00,KHOP_PGP_SIGNED,KHOP_THREADED,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <513514EB.7050107@dancol.org>
Date: Mon, 04 Mar 2013 13:40:59 -0800
From: Daniel Colascione <dancol AT dancol DOT org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Drag a file into emacs-w32 frame
References: <5134CACE DOT 9060900 AT gmail DOT com> <51351188 DOT 9010208 AT cornell DOT edu> <20130304213902 DOT GH4078 AT calimero DOT vinschen DOT de>
In-Reply-To: <20130304213902.GH4078@calimero.vinschen.de>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2TXGUPGAFROHKPGPPHCFX"
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

------enig2TXGUPGAFROHKPGPPHCFX
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 3/4/2013 1:39 PM, Corinna Vinschen wrote:
> On Mar  4 16:26, Ken Brown wrote:
>> On 3/4/2013 11:24 AM, Arthur Tu wrote:
>>> Today when i tried to drag a file whose name containing chinese
>>> characters into emacs, it failed to open.
>>>
>>> Here is the brief review:
>>>
>>> 1. a file with a pure english file name to emacs-32 frame:
>>>
>>>     open successfully.
>>>
>>>
>>> 2. a file with chinese characters in its name to emacs-32 frame:
>>>
>>>      error message: "dnd-open-local-file: Can not read
>>> file:/cygdrive/c/Users/Arthur/Desktop/%20%20%20%20.txt".
>>>     in fact, i tried several times with different name. the name was
>>> always decoded as a punch of "20%", even though different chinese
>>> characters were there.
>>>
>>>
>>> 3. the same file with chinese characters in its name to a emacs-nox
>>> frame(mintty):
>>>
>>>     the file name was pasted into the buffer correctly. chinese
>>> characters were shown correctly. the file wasn't open. (This is what's
>>> expected to happen in terminal session.)
>>>
>>>
>>> So my question was around the situation 2.
>>> How did the emacs-w32 handle the dragged file?
>>
>> The code for handling the file name appears to be in src/w32fns.c.
>> I don't know what the issues are in trying to make it work when the
>> name contains Chinese characters.  Daniel?
>=20
> Cygwin is using UTF-8 as codeset by default.  Is it possible that
> w32fns.c is using *shudder* Windows functions to load the file?  If so,
> it uses the current Windows ANSI codepage, perhaps cp850 or some such.
>=20
> Bottom line: Use Windows functions for the GUI as much as you like.
> But don't use the Windows file API.  Use Cygwin functions for that.  If
> you have to use a Windows functions to fetch the filename, use the
> UNICODE Windows functions (the one with the trailing W) and convert the
> filename to the current Cygwin codeset using cygwin_conv_path
> (CCP_WIN_W_TO_POSIX, ...).
>=20

God no --- we're not using Win32 filesystem API functions in cygw32 Emacs. I
haven't had a chance to take a look at the problem yet, but it's probably j=
ust a
URI-encoding issue. Emacs insists on receiving drag-and-drop events as URIs,
even if they come in as filenames and pop back out the other end as filenam=
es.



------enig2TXGUPGAFROHKPGPPHCFX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlE1FO0ACgkQ17c2LVA10VuvMwCgySRttG8RjgE7GQQNdtStTShl
sLUAnRVLbQbtLWbhbShUbOOgiaZvso+8
=aYzX
-----END PGP SIGNATURE-----

------enig2TXGUPGAFROHKPGPPHCFX--