[Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

[Simon Hausmann]

Hi,


What may be a door for you (or maybe it isn't actually) may be a wall for somebody else. Imagine an individual

contributor who would like to contribute a portion of code that is large enough to for the contributor to make

an explicit copyright/author claim at the top of the file. For KDAB that's easy, but for an individual from other

countries and cultures forcing the choice of an ASCII encoded "version" of their name may be perceived in a

negative way (from "not welcome" to perhaps even "discriminating").


So what's a door and what isn't is subjective, but I really don't see a reason to keep the wall there altogether when

we can remove it with what seems little effort.


Simon

________________________________
From: André Pönitz <apoenitz at t-online.de>
Sent: Monday, January 30, 2017 6:41:54 PM
To: Simon, Hausmann
Cc: Viktor, Engelmann; development at qt-project.org
Subject: Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On Mon, Jan 30, 2017 at 11:23:30AM +0000, Simon, Hausmann wrote:
> 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 :)

Qt source is handled by a variety of tools, not only compilers.

Nowadays they kind of all kind of always support kind of UTF-8, yeah, so
use it, if it works. Fine.

But I absolutely don't get the point of trying to run with my head into
a wall because I know there is a door in the wall on the construction
drawing in this place, even if my eyes tell me it's a couple of feet to
the left.

Andre'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20170201/82d95256/attachment.html>