Re: [Development] Hardcoded strings and qstricmp comparison

2018-11-14 Thread Thiago Macieira
On Wednesday, 14 November 2018 00:34:50 PST Andy Shaw wrote: > For user code I get that we can just say that they should do something like: > > qstricmp(str, QLatin1String("a").latin1()); What we should do is actually have QLatin1String overloads of the functions in questions. We already have

Re: [Development] Hardcoded strings and qstricmp comparison

2018-11-14 Thread Andy Shaw
Edward Welbourne skrev følgende den 14.11.2018, 11:03: Andy Shaw (14 November 2018 09:34) wrote: > ... there may be some problems that are connected to using qstricmp > and other functions that are expecting latin1 strings for one reason > or another. The reason that this might

Re: [Development] Hardcoded strings and qstricmp comparison

2018-11-14 Thread Edward Welbourne
Andy Shaw (14 November 2018 09:34) wrote: > ... there may be some problems that are connected to using qstricmp > and other functions that are expecting latin1 strings for one reason > or another. The reason that this might be a problem is because we are > encoding our source code as UTF-8 and ther

[Development] Hardcoded strings and qstricmp comparison

2018-11-14 Thread Andy Shaw
Hi! In connection to a support case I have been working on it was brought to my attention that there may be some problems that are connected to using qstricmp and other functions that are expecting latin1 strings for one reason or another. The reason that this might be a problem is because we a