On Friday, 7 June 2019 09:23:22 PDT Konstantin Ritt wrote:
> I doubt QByteArray really fits "text" scope.
Yes, it does. It's our main class for managing 8-bit strings and it has a few
text manipulation functions, like toUpper().
> As for QLocale, I think it is a material for the "unicode" scope;
I doubt QByteArray really fits "text" scope.
As for QLocale, I think it is a material for the "unicode" scope; same for
QUnicodeTools, QUnicodeTables, QTextBoundaryFinder and maybe BiDi impl from
QtGui.
Regards,
Konstantin
пт, 7 июн. 2019 г. в 19:01, Edward Welbourne :
> Hi all,
>
> Just to sa
Hi all,
Just to save some confusion when folk hit the need to rebase: I've just
moved (on dev) all date, time and time-zone things from corelib/tools/
to corelib/time/. I shall, in the (hopefully [*]) near future, do the same
for string, byte-array, regex and locale things, into corelib/text/:
ht
On 2019-05-17 10:18, Giuseppe D'Angelo via Development wrote:
QHash ones are bidirectional
Nope.
(Go look yourself, it's too hilarious for spoilers)
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/develop
Hi,
I don't think anybody has tried an emscripten build yet. That said, from a
building perspective it's a regular static build of Qt, emscripten comes with a
cmake toolchain file, it's a single arch build and generally an easy interface,
in my experience working with emscripten. The main issue
