[Development] HEADS-UP: QStringLiteral

Thiago Macieira thiago.macieira at intel.com
Fri Aug 23 17:04:34 CEST 2019

On Thursday, 22 August 2019 23:44:02 PDT Ville Voutilainen wrote:
> > This doesn’t solve the problem that you’re having when you want to use
> > anything outside the ascii range inside “literal”, as the encoding of the
> > source code on disk is not defined. u”…” or u8”…” defines the output
> > encoding (utf16 or utf8), but with the input encoding being undefined,
> > that is not helpful at all for writing portable code.
> Ack. Well, we can vote with our feet, and say that in Qt's realm the
> input encoding is expected to be utf-8.

And we've done that and all of Qt's modules build like that.

We just haven't forced that choice on our users. It's opt-in for them.

But we can use u"" just fine, right now.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products

More information about the Development mailing list