From 0b36942f680bfa9ae88a564f2636aa8286470073 Mon Sep 17 00:00:00 2001 From: Mateusz Konieczny Date: Mon, 22 Nov 2021 15:48:42 +0100 Subject: doc: transcoding is done in addition to search Even if transcoding would be faster than search it would still incur performance penalty. We make this clearer by tweaking the wording. PR #2079 --- GUIDE.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/GUIDE.md b/GUIDE.md index 8b4dfd1e..7a26a4b2 100644 --- a/GUIDE.md +++ b/GUIDE.md @@ -648,9 +648,9 @@ given, which is the default: they correspond to a UTF-16 BOM, then ripgrep will transcode the contents of the file from UTF-16 to UTF-8, and then execute the search on the transcoded version of the file. (This incurs a performance penalty since transcoding - is slower than regex searching.) If the file contains invalid UTF-16, then - the Unicode replacement codepoint is substituted in place of invalid code - units. + is needed in addition to regex searching.) If the file contains invalid + UTF-16, then the Unicode replacement codepoint is substituted in place of + invalid code units. * To handle other cases, ripgrep provides a `-E/--encoding` flag, which permits you to specify an encoding from the [Encoding Standard](https://encoding.spec.whatwg.org/#concept-encoding-get). -- cgit v1.2.3