diff options
author | Thiago Macieira <thiago.macieira@intel.com> | 2014-04-04 10:34:15 -0700 |
---|---|---|
committer | The Qt Project <gerrit-noreply@qt-project.org> | 2014-04-24 10:48:03 +0200 |
commit | bbf37b61d00a6470349b728a4e6982a359e0931c (patch) | |
tree | 25f17afa01732c1e836f553c8737b65e860d31e2 /util | |
parent | f56ef579ba5b1d3adda060fa9c0707e37f9f1baa (diff) |
Document QString's UTF-8 conversion behaviors
We haven't handled the Unicode non-characters specially since Qt 5.2
(since commit 9327bc87c3abf58bb471693b5448cd78e3db1b46), so this part of
the documentation was stale.
Since Qt 5.3 (since 8dd47e34b9b96ac27a99cdcf10b8aec506882fc2), QString
will insert one replacement character for each byte that can't be decoded
properly.
[ChangeLog][Important Behavior Changes][UTF-8 decoding] The QString
UTF-8 decoder changed behavior slightly: when it encounters invalid
sequences, it will insert one replacement character per byte that is
invalid, instead of one replacement character for the whole invalid
length.
Change-Id: Ia4ec78afded9445bbe937311d6be80f71bd1a55f
Reviewed-by: Richard J. Moore <rich@kde.org>
Reviewed-by: Olivier Goffart <ogoffart@woboq.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
Diffstat (limited to 'util')
0 files changed, 0 insertions, 0 deletions