1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

QAnyStringView: fix code point -> code unit in the docs

Browse Source 
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 <thiago.macieira@intel.com>
Reviewed-by: Marc Mutz <marc.mutz@qt.io>
This commit is contained in:
Giuseppe D'Angelo 2022-01-14 17:17:12 +01:00
parent 6ffc8d8eb6
commit 3f06d47e57
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/corelib/text/qanystringview.qdoc
View File

@ -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).