From 3f06d47e5757d7cbc5e21b9cfb2008a9a6510b96 Mon Sep 17 00:00:00 2001 From: Giuseppe D'Angelo Date: Fri, 14 Jan 2022 17:17:12 +0100 Subject: 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 --- src/corelib/text/qanystringview.qdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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). -- cgit v1.2.3