I always find it hilarious how people start debates about UTF-8 vs UTF-16 in string APIs. Let us not forget that in an ideal world, the QString API wouldn't expose the underlying encoding *at all*, and it would be an implementation detail unknown to users.
See Swift's String class for example: https://developer.apple.com/swift/blog/?id=30 If you're thinking in terms of code units instead of in terms of grapheme clusters, you don't truly understand Unicode. And also end up with historical radioactive waste like UTF-16. On Jul 12, 2016, at 5:58 AM, charleyb123 . <charleyb...@gmail.com<mailto:charleyb...@gmail.com>> wrote: On Tue, Jul 12, 2016 at 3:47 AM, Marco Bubke <marco.bu...@qt.io<mailto:marco.bu...@qt.io>> wrote: <snip>, Lets face it, the world is much bigger than Qt, and I think there is much to gain if we integrate better with alien libraries. My understanding is that most alien libraries are not binary-based (i.e., they are ternary or use other forms of multi-valued-logic (MVL)). ;-)) --charley _______________________________________________ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development -- Jake Petroules - jake.petrou...@qt.io<mailto:jake.petrou...@qt.io> Consulting Services Engineer - The Qt Company Qbs build tool evangelist - qbs.io<http://qbs.io>
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
