Re: fixing url-unhex-string for unicode/multi-byte charsets

[Eli Zaretskii]

> Date: Fri, 6 Nov 2020 05:34:46 -0500
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: emacs-devel@gnu.org
> 
> > I believe in the trash case we already know these are file names, so
> > at least some of what eww-decode-url-file-name does is unnecessary,
> > IMO.
> 
> This all started from Arthur Miller's observation that restoring a
> 'remote' file was failing. He said that's a new feature in emacs, that
> one can trash a file over ssh or some other protocol and the file is
> trashed to your local file system. In that case, Arthur pointed out to
> the list that the colon character of the protocol wasn't being decoded.
> Once emacs needs to account for remotes, it needs to account for the
> protocols and urls of those remotes.

A remote file name is not a URL, especially not when we talk about
encoding non-ASCII characters.  The conventions and the defaults are
different.