On Wednesday 11 February 2015 04:05:02 Konstantin Ritt wrote: > Previously you said QString::data() must return QChar* (and not a generic > uchar*), so that QString with an adaptive storage would have to silently > convert the internal encoding into the one represented by QChar. > If QString has a UCS-4 indexes and length() that counts the amount of UCS-4 > codepoints, one would expect QString::data() to return UCS-4*, right?
Right. But the question stands: what's the advantage in doing that over doing UTF-16, which is what we already have. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
