summaryrefslogtreecommitdiffstats
path: root/tests/auto/qscriptengine/translatable-unicode.js
Commit message (Collapse)AuthorAgeFilesLines
* Make qsTr() work with Unicode (non-Latin-1) stringsKent Hansen2010-11-081-0/+9
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