all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: fixing url-unhex-string for unicode/multi-byte charsets
Date: Fri, 6 Nov 2020 05:27:56 -0500	[thread overview]
Message-ID: <20201106102756.e2ctvpjruenatud5@E15-2016.optimum.net> (raw)
In-Reply-To: <83wnyy9akw.fsf@gnu.org>

On 2020-11-06 10:02, Eli Zaretskii wrote:
> I made a suggestion in that discussion, I will repeat some of them
> here:

Yeah, but they don't work.

> So, for file names, something like the below should do the job
> simpler:
>
>   (decode-coding-string (url-unhex-string STR)
>                         (or file-name-coding-system
> 			    (default-value 'file-name-coding-system)))

Try it. To reproduce, touch and then trash a file named some two Hebrew
words delimited by a space. Navigate to the trash directory's 'info'
sub-directory and extract the 'path' value from the file's meta-data
.info file. That's the string we need to decode. Apply the string to
your solution and see that you do not get the space-delimited two Hebrew
words.

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0



  reply	other threads:[~2020-11-06 10:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06  7:47 fixing url-unhex-string for unicode/multi-byte charsets Boruch Baum
2020-11-06  8:02 ` Eli Zaretskii
2020-11-06 10:27   ` Boruch Baum [this message]
2020-11-06 12:04     ` Eli Zaretskii
2020-11-06 12:28       ` Boruch Baum
2020-11-06 13:34         ` Eli Zaretskii
2020-11-06 14:59           ` Stefan Monnier
2020-11-06 15:04             ` Eli Zaretskii
2020-11-08  9:12               ` Boruch Baum
2020-11-08 13:39                 ` Stefan Monnier
2020-11-08 15:07                 ` Eli Zaretskii
2020-11-06 14:38     ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2020-11-06  7:54 Boruch Baum
2020-11-06  8:05 ` Eli Zaretskii
2020-11-06 10:34   ` Boruch Baum
2020-11-06 12:06     ` Eli Zaretskii

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=20201106102756.e2ctvpjruenatud5@E15-2016.optimum.net \
    --to=boruch_baum@gmx.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.