Making a warning go away for compilers that we know support utf-8 may not come at the price of your life :)
I for one am all in favor of requiring just the Qt source code (not talking about customer code) to be encoded in a 24 year old standard and add all the necessary flags to the compilers to make them understand it instead of producing a warning. We practically support three different front-ends: GCC, clang and MSVC. All three - MSVC with the help of an option - can grok UTF-8. Let's use it at least inside Qt :) Simon ________________________________ From: Development <development-bounces+simon.hausmann=qt...@qt-project.org> on behalf of Viktor Engelmann <viktor.engelm...@qt.io> Sent: Monday, January 30, 2017 12:06:19 PM To: development@qt-project.org Subject: Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows? Am 30.01.2017 um 11:40 schrieb Giuseppe D'Angelo: > Il 30/01/2017 11:35, Viktor Engelmann ha scritto: >> As far as I can see, all our codes *are* UTF-8 encoded (a least they >> should be, IMHO), so why would we sneak our UTF8 in behind it's back (in >> 2017!) instead of just telling the compiler the encoding we are using? > So *all* of our compilers happily support UTF-8 encoded sources? I wouldn't bet my life on that (especially not for windows!) -- Viktor Engelmann Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin viktor.engelm...@qt.io +49 151 26784521 http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin Registergericht: Amtsgericht Charlottenburg, HRB 144331 B _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
