Hi, actually in my experience with MSVC2013 it's the other way around,
i.e. as long as MSVC doesn't see any BOMs, you can use UTF-8 strings.
But if you edit it once in Notepad, *boom* and you lose that availabilty.
For example, create a new Widget app, insert this line in MainWindow.cpp
just be
Hi Jochen,
if I remember correctly, MSVC (at least older versions) needs a BOM
(Byte Order Mark) at the file's beginning to detect UTF-8 encoded files.
Then it should work even without C++11 string constants.
Maybe that's the reason for your problems.
Best regards,
André
Am 07.09.2015 um 11:49
> C++11 introduced new UTF-8 string constans, so it should be possible to
> write the following:
> QStringLiteral(u8"This is a Unicode Character: \u2018.")
> and all C++11 compiler should compile it without warnings. Right?
> Shall we change the coding style and allow the new UTF-8 string
> lite
Hi Immanuel,
Please update your Visual Studio installation. IIRC you need at least
Service Pack 2. I guess this should be part of the README.
David
Am 07.09.2015 um 10:03 schrieb Immanuel Weber:
Hi all,
I just wanted to update my x64 build of QtCreator to 3.5.0, but
unfortunately that fail
Hi all,
I just wanted to update my x64 build of QtCreator to 3.5.0, but
unfortunately that failed.
I get the following error:
utf8stringvector.cpp(44) : error C2664:
'QVector::QVector(QVector &&)' : cannot convert
argument 1 from 'std::initializer_list' to 'int'
No user-defined-conversion operator