Re: dired-do-find-regexp failure with latin-1 encoding

[Eli Zaretskii <eliz@gnu.org>]

> Cc: stephen.berman@gmx.net, emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 28 Nov 2020 23:04:10 +0200
> 
> >> Are you sure about that? Are we sure it won't make searching binary
> >> files slower, for example?
> > 
> > It will be slower, but more useful: by default Grep just says "Binary
> > file foo matches".
> 
> Do we want to search the "binary" files at all?

We don't.  I still hope to understand why -a was needed in this case.
Stephen?

> > We should support Grep regardless, since not everyone will have
> > ripgrep.  And in any case, "C-x RET c" will be needed with it as well,
> > no?
> 
> I'd have to test it explicitly to say for sure, but:
> 
>    ripgrep supports searching files in text encodings other than UTF-8,
>    such as UTF-16, latin-1, GBK, EUC-JP, Shift_JIS and more. (Some
>    support for automatically detecting UTF-16 is provided. Other text
>    encodings must be specifically specified with the -E/--encoding flag.)
> 
> https://blog.burntsushi.net/ripgrep/#pitch

What is not clear to me is whether the _output_ is always in some
fixed encoding, like UTF-8.  That doesn't seem to be stated in the
docs there.