bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#36085: 26.2; find-dired octal escapes instead of Cyrillic text


From: Eli Zaretskii
Subject: bug#36085: 26.2; find-dired octal escapes instead of Cyrillic text
Date: Sat, 08 Jun 2019 15:20:18 +0300

> From: Nikita <grindeg@yandex.ru>
> Date: Tue, 4 Jun 2019 08:43:06 +0500
> 
> When i open dired, go to the needed directory, run "M-x dired-find"
> "-name "*Портрет*" (or anything at all that will give some results)
> results come back with octal escapes instead of Cyrillic letters.
> I cannot open pictures that it finds for example.

Turns out the octal escapes are produced by 'find' itself in this
case.  Try the following command in that directory from the shell
prompt:

   find . \( -iname "*Портрет*" \) -ls

and you will see the same octal escape instead of the Cyrillic
characters.  The man page for 'find' clearly documents this, under
"Unusual Filenames":

 Unusual characters are handled differently by various actions, as
 described below.
 [...]

   -ls, -fls
         Unusual characters are always escaped.  White space,  backslash,
         and  double  quote characters are printed using C-style escaping
         (for example `\f', `\"').  Other unusual characters are  printed
         using  an octal escape.  Other printable characters (for -ls and
         -fls these are the characters between octal 041  and  0176)  are
         printed as-is.

What this means is that any non-ASCII character will be converted to a
series of octal escapes.  IMO, this is a terrible misfeature in GNU
Findutils, as such "handling" of non-ASCII characters has no place in
today's global environment.

I suggest to report this bug to the GNU Findutils developers.

Thanks.

P.S. Emacs could perhaps go above and beyond the call of duty, and
attempt to convert the octal escapes back to readable text.  But I
don't think we should do it, as it's a clear bug in 'find'.
Nonetheless, if someone wants to submit patches to do such a
conversion, I won't block them.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]