On 27-7-2015 18:13, Thiago Macieira wrote: > On Monday 27 July 2015 08:44:30 Knoll Lars wrote: >> I can understand the issues that non latin speakers are facing with this >> well. I’ve often used qDebug() to debug non latin use cases, and in 90% of >> the cases I just want to know what the string reads. The unicode content >> of it is interesting to me in only 10% of the cases. For most users not >> debugging Qt’s internals I would assume that ratio to be more like 99 to 1. > As I said in my email, the problem is that you will not turn this on for those > 10% of the cases until you've already lost data, either visibly or really. I'm > counting ambiguity and homographs as apparent data loss because it will send > you down the wrong debugging path. In that case, I think your solution _causes_ data loss when debugging path-related issues in Windows. If paths get their separators doubled all of a sudden, then that is certainly going to send people down the wrong debugging track.
André _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development