diff options
| author | Kent Hansen <kent.hansen@nokia.com> | 2010-11-08 12:25:30 (GMT) |
|---|---|---|
| committer | Kent Hansen <kent.hansen@nokia.com> | 2010-11-08 14:46:29 (GMT) |
| commit | 27e77b7ceeeffe9227b5b96fdd63e3433e0eb63e (patch) | |
| tree | 5f28fc510bd4649a8a86fd1cb9b5a39927369a7f /doc/src/snippets/code/doc_src_groups.cpp | |
| parent | d48a324d6670b14348d546db6a739ee138dab1e2 (diff) | |
| download | Qt-27e77b7ceeeffe9227b5b96fdd63e3433e0eb63e.zip Qt-27e77b7ceeeffe9227b5b96fdd63e3433e0eb63e.tar.gz Qt-27e77b7ceeeffe9227b5b96fdd63e3433e0eb63e.tar.bz2 | |
Make qsTr() work with Unicode (non-Latin-1) strings
Converting the source string/context/comment to Latin-1 is very
broken, since JS strings are UTF-16.
The strings should be converted to UTF-8, which should also be
the default encoding for qsTranslate().
Effectively, this bug meant that only Latin-1 characters could
be used in source strings; the translations themselves could
have non-Latin-1 characters. But there was data loss in the
case where you passed a source string for which no translation
was found (since the Latin-1-ized string would be returned).
Task-number: QTBUG-14989
Reviewed-by: Jedrzej Nowacki
Diffstat (limited to 'doc/src/snippets/code/doc_src_groups.cpp')
0 files changed, 0 insertions, 0 deletions