[Development] Why can't QString use UTF-8 internally?

Konstantin Ritt ritt.ks at gmail.com
Tue Feb 10 21:37:41 CET 2015

Yes, that would be an ideal solution. Unfortunately, that would also break
a LOT of existing code.
In Qt4 times, I was doing some experiments with the QString adaptive
storage (similar to what NSString does behind the scenes).


2015-02-11 0:22 GMT+04:00 Oswald Buddenhagen <
oswald.buddenhagen at theqtcompany.com>:

> On Tue, Feb 10, 2015 at 10:58:58PM +0400, Konstantin Ritt wrote:
> > Despite of what http://utf8everywhere.org/#conclusions says, UTF-16 is
> not
> > the worst choice; it is a trade-off between the performance and the
> memory
> > consumption in the most-common use case (spoken languages and mixed
> > scripts).
> >
> well, the question is whether a trade-off is actually necessary? why not
> use an algorithmically efficient format (ucs4) where it matters (caches
> of font rendering backends, i suppose?) and utf8 everywhere else?
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20150211/701740fd/attachment.html>

More information about the Development mailing list