From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 13907@debbugs.gnu.org
Subject: bug#13907: 24.3.50; cygw32 build mishandles drag-n-dropped file with non-ASCII characters in name
Date: Sat, 09 Mar 2013 10:09:05 +0200 [thread overview]
Message-ID: <83r4jpxae6.fsf@gnu.org> (raw)
In-Reply-To: <513A521D.9090902@cornell.edu>
> Date: Fri, 08 Mar 2013 16:03:25 -0500
> From: Ken Brown <kbrown@cornell.edu>
> CC: Daniel Colascione <dancol@dancol.org>, 13907@debbugs.gnu.org
>
> The value of file-name that is passed to
> cygwin-convert-file-name-from-windows is "C:\\cygwin\\tmp\\\334.txt".
> The converted file name is then "/tmp/ .txt".
The appearance of a blank (or a question mark) instead of a character
is usually a tell-tale sign of a botched character conversion.
For example, when I drag-n-drop into a native w32 Emacs a file name
that includes characters not from the system codepage, I get this:
dnd-open-local-file: Can not read file:D%3A/gnu/ispell-3.3.02.w32/dictionaries/Tatar-Rus-%3Fngliz%20s%3Fzlege.htm
(%3F is the question mark.)
next prev parent reply other threads:[~2013-03-09 8:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 17:18 bug#13907: 24.3.50; cygw32 build mishandles drag-n-dropped file with non-ASCII characters in name Ken Brown
2013-03-08 19:42 ` Eli Zaretskii
2013-03-08 20:06 ` Eli Zaretskii
2013-03-08 20:33 ` Eli Zaretskii
2013-03-08 20:53 ` Eli Zaretskii
2013-03-08 21:03 ` Ken Brown
2013-03-09 8:09 ` Eli Zaretskii [this message]
2013-03-08 21:25 ` Daniel Colascione
2013-03-09 3:03 ` Daniel Colascione
2013-03-09 3:03 ` Daniel Colascione
2013-03-09 8:32 ` Eli Zaretskii
2013-03-09 8:37 ` Daniel Colascione
2013-03-09 8:51 ` Eli Zaretskii
2013-03-09 8:37 ` Daniel Colascione
2013-03-10 23:00 ` Daniel Colascione
2013-03-11 9:51 ` Ken Brown
2013-03-09 12:16 ` Ken Brown
2013-03-09 19:31 ` Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r4jpxae6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13907@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.