[Development] Let's please drop MSVC 2013 for 5.10

Thiago Macieira thiago.macieira at intel.com
Fri Jun 16 22:25:34 CEST 2017

On Friday, 16 June 2017 13:10:10 PDT Henry Skoglund wrote:
> That question reminds me of the discussion last August
> http://lists.qt-project.org/pipermail/interest/2016-August/023882.html
> about Unicode code points in MSVC and how to fix so that
> tr("Co├Ârdinaat") or tr("Co\u00F6rdinaat"); worked with old MSVC compilers.
> My workaround: use raw UTF8 hex bytes: tr("Co\xC3\xB6rdinaat");
> I think using that stunt should allow you to encode any non-ASCII
> characters inside a QStringLiteral with any compiler that supports "\x..."

You'd be wrong. That trick works for tr("Co\xC3\xB6rdinaat"); and the QString 

It does NOT work for QStringLiteral.

So to answer my question:
Q:	How does one create a QStringLiteral containing non-ASCII characters that 
will work on all our supported compilers?
A:	You don't, unless you drop MSVC 2013 from that list in the first place.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list