Hi
If I forgot to tell you that we have a maintenance break, so did I also forget
to tell you that it is over. Aprox 8-9 hours ago I launched the CI and builds
began passing again.
-Tony
From: Tony Sarajärvi
Sent: tiistai 22. tammikuuta 2019 18.24
To: development@qt-project.org
Subject:
On Tuesday, 22 January 2019 09:01:16 PST Arnaud Clère wrote:
> QByteArray is the official way to deal with utf8 strings but:
> 1. This discussion shows it is not as known as it should be and I argue the
> name does not help
> 2. Dealing with binary data and all kind of string
> encodings in a
On Tuesday, 22 January 2019 11:02:22 PST Matthew Woehlke wrote:
> On 18/01/2019 11.09, Thiago Macieira wrote:
> > As for strings, the QString constructor takes UTF-8 input, but however
> > fast
> > the decoder is, it's still slightly slower than the Latin1 decoder. So if
> > your string is purely
On 18/01/2019 11.09, Thiago Macieira wrote:
> As for strings, the QString constructor takes UTF-8 input, but however fast
> the decoder is, it's still slightly slower than the Latin1 decoder. So if
> your
> string is purely US-ASCII, using QLatin1String is recommended.
...but I assume
> Original Message-
> From: Jason H
>
> > From: "Arnaud Clère"
> >
> > > -Original Message-
> > > From: Allan Sandfeld Jensen
> > >
> > > Use QByteArray when you can.
> >
> > I think a QUtf8String class derived from QByteArray would help a lot making
> > this happen in the
On Tuesday, 22 January 2019 06:49:51 PST Jason H wrote:
> typedef QSymbolSequence QLatin1String;
> typedef QSymbolSequence QByteArray;
> typedef QSymbolSequence QByteArray;
> typedef QSymbolSequence QString;
>
> So they can have the same API? It really seems to me that the issue is
> storage, not
Sorry all, but we forgot to publicly announce that our firewall change is
proceeding to the next phase right now. This means that for the next hours some
of our web pages are going offline and the CI is brought down.
I'll inform you when all is up and running again.
-Tony
> Sent: Monday, January 21, 2019 at 9:51 AM
> From: "Arnaud Clère"
> To: "Allan Sandfeld Jensen" , "development@qt-project.org"
>
> Subject: Re: [Development] Qt6: Adding UTF-8 storage support to QString
>
> > -Original Message-
> > From: Allan Sandfeld Jensen
> >
> > On Dienstag,
Thanks JP!
It's going to be hard to follow in your footsteps, but I'll do my best. :)
Thanks to those who +1'd as well.
On 1/22/19, 2:51 PM, "Frederik Gladhorn" wrote:
Hi,
It's been a while, so I'd like to congratulate Mitch on becoming maintainer
for Controls 2 :)
Hi,
It's been a while, so I'd like to congratulate Mitch on becoming maintainer
for Controls 2 :)
I'll update the wiki.
Cheers,
Frederik
On mandag 26. november 2018 19:39:03 CET J-P Nurmi wrote:
> Hi all,
>
> As you may have noticed, I haven't been actively working on Qt Quick
> Controls 2
Hi,
In order to improve transparency and visibility (after getting some
constructive and well deserved criticism):
We have received a proposal of dropping UWP 2015 x86 builds in favour of MinGW
32-bit packages. We looked at this today and agreed that this can be done, and
it should be our
First issue on 2019!
Generally, CI/COIN was in a very good mood after the new year update. Then we
met https://bugreports.qt.io/browse/QTBUG-73116 ,
tst_QString::localeAwareCompare fails (dev) and a few other issues. Now it
looks like most of them got fixed already.
Merges
* Submodules
Hi all,
Qt for WebAssembly shipped as a tech preview for 5.12, and for 5,13 we want to
fill in some of the missing pieces, and also make Q_OS_WASM a supported
platform. Supported here does not mean that everything that does not work today
will work, but rather that what we claim will work
13 matches
Mail list logo
