From fe008233306eebca44770d3d4411313e18ced3c3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C3=A1draig=20Brady?= Date: Sat, 28 Mar 2026 16:18:41 +0000 Subject: [PATCH] doc: cut: clarify that combining characters are not treated specially This is for consistency with other implementations and since the interface separates -b and -c it might in future support -g (graphemes). Normalizing content with a filter seems like the most appropriate approach anyway, as there are various normalizations possible including case etc. rather than baking that into every tool --- doc/coreutils.texi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/coreutils.texi b/doc/coreutils.texi index 4352711b4..0f9d3e276 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -6164,8 +6164,9 @@ string between ranges of selected bytes. @optItemx{cut,--characters,=@var{character-list}} Select for printing only the characters in positions listed in @var{character-list}. Tabs and backspaces are -treated like any other character; they take up 1 character. If an -output delimiter is specified, (see the description of +treated like any other character; they take up 1 character. +Combining characters are considered as separate characters. +If an output delimiter is specified, (see the description of @option{--output-delimiter}), then output that string between ranges of selected characters.