Re: master 6011d39b6a: Fix drag-and-drop of files with multibyte filenames

[Eli Zaretskii]

> --- a/lisp/select.el
> +++ b/lisp/select.el
> @@ -630,20 +630,20 @@ two markers or an overlay.  Otherwise, it is nil."
>          (xselect--encode-string 'TEXT (buffer-file-name (nth 2 value))))
>      (if (and (stringp value)
>               (file-exists-p value))
> -        (xselect--encode-string 'TEXT (expand-file-name value)
> -                                nil t)
> +        ;; Motif expects this to be STRING, but it treats the data as
> +        ;; a sequence of bytes instead of a Latin-1 string.
> +        (cons 'STRING (encode-coding-string (expand-file-name value)
> +                                            'raw-text-unix))

I don't think I understand this change.  raw-text basically doesn't do
any conversion, except if the text includes raw bytes.  Is that the
problem here, and if so, how come a file name can include raw bytes in
its name?  And what does "Motif expects this to be STRING, but it
treats the data as a sequence of bytes instead of a Latin-1 string"
mean in this context?  The difference between raw bytes and Latin-1
strings is only meaningful to Emacs; how does Motif distinguish
between them?