all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 6011d39b6a: Fix drag-and-drop of files with multibyte filenames
Date: Sun, 05 Jun 2022 21:07:06 +0800	[thread overview]
Message-ID: <87h74zz2bp.fsf@yahoo.com> (raw)
In-Reply-To: <83h74z9sp1.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 05 Jun 2022 15:54:18 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Yes.  Sorry, I forgot that the code was in Lisp, not C.
>
>> > If some program other than Emacs is the target of the drop, raw bytes
>> > produced from raw-text will not be meaningful for it.
>> 
>> Why not?  Aren't those bytes equivalent to a C string describing a file
>> name that can be passed to `open'?
>
> Not necessarily.  First, non-ASCII characters can be encoded in
> different ways, and the other program might not necessarily support
> more than just the locale's encoding.  And second, any characters to
> which Emacs gives codepoints beyond the Unicode codespace (something
> that is rare, but it does happen) will not be understood by the other
> programs at all, because their codepoints are completely private to
> Emacs.

[...]

> <Shrug> I guess that other code is also incorrect, and was never
> seriously tested with non-ASCII file names outside of UTF-8 locales.
> Try Emacs whose file-name-coding-system is iso-2022-jp or somesuch.

That makes sense now, yes.  Thanks.



      reply	other threads:[~2022-06-05 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05  9:21 master 6011d39b6a: Fix drag-and-drop of files with multibyte filenames Eli Zaretskii
2022-06-05 10:00 ` Po Lu
2022-06-05 10:31   ` Eli Zaretskii
2022-06-05 11:42     ` Po Lu
2022-06-05 12:54       ` Eli Zaretskii
2022-06-05 13:07         ` Po Lu [this message]

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=87h74zz2bp.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.