On 1/31/21 8:10 AM, Paulie Pena IV wrote:
Are there any plans for adding UTF-16 and UTF-32 file support to grep?
No.
I doubt whether it'd be worth the hassle, just as I doubt whether it'd
be worth adding support for lots of similar but more-useful features
(such as grepping through
Supporting Unicode means it should also support UTF-16 and UTF-32 files,
which grep does not.
Look at the insane number of hoops this person had to do to workaround this
major issue (and then it doesn't even print out the matching lines and just
says "Binary file ... matches"):
time
options or tweak the https://en.wikipedia.org/wiki/Environment_variable -s.
Also see https://beyondgrep.com/ .
> Kind regards
>
> -Original Message-
> From: Shlomi Fish
> Sent: Saturday, August 8, 2020 17:16
> To: ca...@kwpg.info
> Cc: 42...@debbugs.gnu.org
>
: GREP does not support Unicode
Hi Carlo!
On Sat, 8 Aug 2020 15:13:40 +0200
wrote:
> Its 2020.
>
> GREP really should support Unicode. (UTF-16, UTF-8, with and without
> signature) Format recognition wouldn't have to be automatic; command
> line switches would be sufficient.
&
Hi Carlo!
On Sat, 8 Aug 2020 15:13:40 +0200
wrote:
> Its 2020.
>
> GREP really should support Unicode. (UTF-16, UTF-8, with and without
> signature) Format recognition wouldn't have to be automatic; command line
> switches would be sufficient.
>
From what I recall gnu grep has supported
Its 2020.
GREP really should support Unicode. (UTF-16, UTF-8, with and without signature)
Format recognition wouldn't have to be automatic; command line switches would
be sufficient.
I am using version Git for Windows v2.25.0
Kind regards
