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

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 4352711b4432fdbde4e07107d39e979cad743c3f..0f9d3e276a454b5ba7c7fca0a60cf9371655ca76 100644 (file)
--- 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.