diff options
authorGiuseppe D'Angelo <>2022-01-14 17:17:12 +0100
committerGiuseppe D'Angelo <>2022-01-16 09:57:07 +0100
commit3f06d47e5757d7cbc5e21b9cfb2008a9a6510b96 (patch)
parent6ffc8d8eb6c44fbd51e37770e7013c4610ead96d (diff)
QAnyStringView: fix code point -> code unit in the docs
The docs are saying that QAnyStringView sizes are measured in terms of code units of the underlying encoding, not code points. Pick-to: 6.3 6.2 Change-Id: Ic72ffd122e45631e8626c9d57ec24ca348918424 Reviewed-by: Thiago Macieira <> Reviewed-by: Marc Mutz <>
1 files changed, 1 insertions, 1 deletions
diff --git a/src/corelib/text/qanystringview.qdoc b/src/corelib/text/qanystringview.qdoc
index ec4f1c5a42..743e389a8f 100644
--- a/src/corelib/text/qanystringview.qdoc
+++ b/src/corelib/text/qanystringview.qdoc
@@ -103,7 +103,7 @@
\section2 Sizes and Sub-Strings
All sizes and positions in QAnyStringView functions are in the
- encoding's code points (that is, UTF-16 surrogate pairs count as
+ encoding's code units (that is, UTF-16 surrogate pairs count as
two for the purposes of these functions, the same as in QString,
and UTF-8 multibyte sequences count as two, three or four,
depending on their length).