Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-28 Thread Andreas Aardal Hanssen
2015-07-28 9:50 GMT+02:00 Robert Iakobashvili corobe...@gmail.com: On Tue, Jul 28, 2015 at 11:48 AM, Marc Mutz marc.m...@kdab.com wrote: On Monday 27 July 2015 20:44:48 Thiago Macieira wrote: On Monday 27 July 2015 21:41:44 NIkolai Marchenko wrote: Yes,but this requires making override

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-28 Thread Robert Iakobashvili
On Tue, Jul 28, 2015 at 11:48 AM, Marc Mutz marc.m...@kdab.com wrote: On Monday 27 July 2015 20:44:48 Thiago Macieira wrote: On Monday 27 July 2015 21:41:44 NIkolai Marchenko wrote: Yes,but this requires making override visible in every file of the project. We can solve this by having a

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-28 Thread Marc Mutz
On Monday 27 July 2015 20:44:48 Thiago Macieira wrote: On Monday 27 July 2015 21:41:44 NIkolai Marchenko wrote: Yes,but this requires making override visible in every file of the project. We can solve this by having a global #ifdef that can change the setting. Or an environment variable,

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-28 Thread Rutledge Shawn
On 28 Jul 2015, at 10:48, Marc Mutz marc.m...@kdab.com wrote: On Monday 27 July 2015 20:44:48 Thiago Macieira wrote: On Monday 27 July 2015 21:41:44 NIkolai Marchenko wrote: Yes,but this requires making override visible in every file of the project. We can solve this by having a global

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-28 Thread Matthew Woehlke
On 2015-07-28 04:29, Andreas Aardal Hanssen wrote: Isn't this needless convenience? Yet another environment variable that needs documenting? If you want to inspect the contents of a QString, can't you just add the suitable escape code to your own code? Forcing qPrintable() or qUtf8Printable()

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-28 Thread Daniel Levin
I would repeat what I said in JIRA. Everything that Thiago explained makes sense to me as soon as it does not break behavior of existing applications. If global flag to enable escaping of QString contents is going to be introduced then it should be disabled by default. On changes that might

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-28 Thread NIkolai Marchenko
People were warned in the changelog. I've already quoted Adams in JIRA, but this is exactly how changelog warnen users of Qt about this change: https://youtu.be/VGLFweev_iI?t=386 Among panicking customers not understanding wtf is happening, unintelligible message, posted in the wrong place and

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-28 Thread Thiago Macieira
On Tuesday 28 July 2015 09:44:23 Matthew Woehlke wrote: While I'm generally trying to stay out of this debate, I'd like to toss in that a QString → QString or QString → QByteArray function that converts from raw to either C-style escaped or HTML-style escaped (or for bonus points, both), AND

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-28 Thread Thiago Macieira
On Tuesday 28 July 2015 18:42:20 NIkolai Marchenko wrote: People were warned in the changelog. I've already quoted Adams in JIRA, but this is exactly how changelog warnen users of Qt about this change: https://youtu.be/VGLFweev_iI?t=386 Among panicking customers not understanding wtf is

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Olivier Goffart
On Monday 27. July 2015 01:25:18 NIkolai Marchenko wrote: Hi! We (Russian Qt community) have a situation we could not resolve with Thiago Macieira in bug tracker, so have to ask for Chief Maintainer's attention. The bug in question is there: https://bugreports.qt.io/browse/QTBUG-47316 [...]

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Thiago Macieira
On Monday 27 July 2015 01:25:18 NIkolai Marchenko wrote: Hi! We (Russian Qt community) have a situation we could not resolve with Thiago Macieira in bug tracker, so have to ask for Chief Maintainer's attention. The bug in question is there: https://bugreports.qt.io/browse/QTBUG-47316 Yes, I

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Thiago Macieira
On Monday 27 July 2015 20:52:24 NIkolai Marchenko wrote: Let's make it harder, can you guesss that it even is a link to paypal website with qDebug() as you intend it to work without copypasting? раураl.соm ? Hint: only 2 letters here are in english. With qDebug() as it is in Qt 5.5, it

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread NIkolai Marchenko
The problem with your approach to qDebug is that it only works well where most of the text is in English and only individual letters are unicode. Once we venture into the territory of debugging 50%+ non-latin, it will be impossible to extract any useful information from debug output at a glance.

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread NIkolai Marchenko
Question, how much do you think this use case happens for non-latin users compared to the one I, and Knoll Lars are arguing about? 2015-07-27 20:25 GMT+03:00 Thiago Macieira thiago.macie...@intel.com: On Monday 27 July 2015 09:05:29 Thiago Macieira wrote: а, which was the attack vector for

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Thiago Macieira
On Monday 27 July 2015 09:05:29 Thiago Macieira wrote: а, which was the attack vector for homograph sites like pаypal.com or pаypаl.com or раураl.com or other permutations of the letters. A control Question: which of the three is the legit website? And what method did you use to find out?

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread NIkolai Marchenko
Let's make it harder, can you guesss that it even is a link to paypal website with qDebug() as you intend it to work without copypasting? раураl.соm ? Hint: only 2 letters here are in english. 2015-07-27 20:25 GMT+03:00 Thiago Macieira thiago.macie...@intel.com: On Monday 27 July 2015

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread NIkolai Marchenko
Once we venture into the territory of debugging 50%+ non-latin, it will be impossible to extract any useful information from debug output at a glance. And that is the situation, where aforementioned flag to change the behaviour in one place will be VERY useful. Unlike your suggestion of fixing

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Ruslan Nigmatullin
27.07.2015, 11:01, "NIkolai Marchenko" enmarantis...@gmail.com: Once we venture into the territory of debugging 50%+ non-latin, it will be impossible to extract any useful information from debug output at a glance. And that is the situation, where aforementioned flag to change the behaviour in one

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Thiago Macieira
On Monday 27 July 2015 21:41:44 NIkolai Marchenko wrote: Yes,but this requires making override visible in every file of the project. We can solve this by having a global #ifdef that can change the setting. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread NIkolai Marchenko
\u0440\u0430\u0443\u0440\u0430l.\u0441\u043em Can you really tell at a glance what exactly you are looking at here without consulting the oracle or, at least, reencoding it to readable format? On Mon, Jul 27, 2015 at 9:22 PM, Thiago Macieira thiago.macie...@intel.com wrote: On Monday 27 July

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Thiago Macieira
On Monday 27 July 2015 21:27:23 NIkolai Marchenko wrote: \u0440\u0430\u0443\u0440\u0430l.\u0441\u043em Oh, really? Note, I said, without copypasting to uncode converter. It's quite evident it's not a link to paypal.com because I can't see paypal there. -- Thiago Macieira - thiago.macieira

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread NIkolai Marchenko
Oh, but now you KNOW that it is a misspeled link to paypal. In real situation you won't have this forward knowlegde. On Mon, Jul 27, 2015 at 9:43 PM, Thiago Macieira thiago.macie...@intel.com wrote: On Monday 27 July 2015 21:27:23 NIkolai Marchenko wrote:

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Andreas Aardal Hanssen
On 27 Jul 2015, at 21:14, Thiago Macieira thiago.macie...@intel.com wrote: On Monday 27 July 2015 21:50:15 NIkolai Marchenko wrote: Oh, but now you KNOW that it is a misspeled link to paypal. In real situation you won't have this forward knowlegde. The point is that I have all of the

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread NIkolai Marchenko
Yes,but this requires making override visible in every file of the project. On Mon, Jul 27, 2015 at 9:34 PM, Ruslan Nigmatullin euroeles...@yandex.ru wrote: 27.07.2015, 11:01, NIkolai Marchenko enmarantis...@gmail.com: Once we venture into the territory of debugging 50%+ non-latin, it will

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Thiago Macieira
On Monday 27 July 2015 21:50:15 NIkolai Marchenko wrote: Oh, but now you KNOW that it is a misspeled link to paypal. In real situation you won't have this forward knowlegde. The point is that I have all of the information I need. If I see a debug output saying: ClassName::openLink: trying to

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread NIkolai Marchenko
\u0440\u0430\u0443\u0440\u0430l.\u0441\u043em Oh, really? Note, I said, without copypasting to uncode converter. On Mon, Jul 27, 2015 at 9:22 PM, Thiago Macieira thiago.macie...@intel.com wrote: On Monday 27 July 2015 20:52:24 NIkolai Marchenko wrote: Let's make it harder, can you guesss

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Thiago Macieira
On Monday 27 July 2015 22:01:26 Andreas Aardal Hanssen wrote: On 27 Jul 2015, at 21:14, Thiago Macieira thiago.macie...@intel.com wrote: On Monday 27 July 2015 21:50:15 NIkolai Marchenko wrote: Oh, but now you KNOW that it is a misspeled link to paypal. In real situation you won't have

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Marc Mutz
On Monday 27 July 2015 00:25:18 NIkolai Marchenko wrote: (I am not entirely sure why I haven't received at least a notification of why this post has not appeared the first time I tried to send it, so here we go again. Btw, it was Thiago Macieira himself who actually suggested I mail this list)

Re: [Development] Backwards compatibiltiy break in Qt 5.5

2015-07-27 Thread Konstantin Ritt
My first instinct was suggesting MS to support Unicode in their console... but then I tried to reproduce the described issue on OS X and succeeded. qDebug() this is сообщение на русском; which I'd expect to be treated like a byte array, gives me this is сообщение на русском though qDebug()

[Development] Backwards compatibiltiy break in Qt 5.5

2015-07-26 Thread NIkolai Marchenko
(I am not entirely sure why I haven't received at least a notification of why this post has not appeared the first time I tried to send it, so here we go again. Btw, it was Thiago Macieira himself who actually suggested I mail this list) Hi! We (Russian Qt community) have a situation we could