> > > You're misrepresenting the argument. QString doesn't support other > encodings > > because UTF-16 is the best for the task at hand and we have too much > legacy to > > support. Because of that, QCollator only supports UTF-16. > > I buy the legacy argument but I don't buy that utf 16 is the best > encoding. I think because of legacy we cannot change QString but I think we > should still support UTF 8 better. >
So what? This doesn't change the fact UTF-16 has advantages over UTF-8 and thus QString's backing storage is UTF-16 - and won't be changed to anything else. Konstantin
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
