https://www.youtube.com/watch?v=cHrrR3KhvUk
Thanks for the insight into what is coming up. I had a minor panic attack
though, which seemed to be shared with the first person to ask a question. If
the property bindings are lazy evaluated, then all my QML code will be broken.
I actively exploit t
>
> QUtf8StringIterator can be easily added to extract Unicode codepoints from
> the UTF-8 string like QStringIterator exists for the same in UTF-16.
>
I have discovered QStringIterator in KDAB blog, it is nice, thanks!
A QUtf8StringIterator would boost Qt utf8 support like easily
splitting/filter
On 5/16/20 6:16 PM, Thiago Macieira wrote:
That opens a philosophical question. In:
QString s = u"a a\u0301"; // U+0301 COMBINING ACUTE ACCENT
s.replace('a', 'b');
Should we now have a b with accent? (b́)
It's not philosophical at all, it's a defining question: at which level
does
On 15/05/2020 14.31, Thiago Macieira wrote:
> Python's bstr still behaves string-like and has methods like
> QByteArray::indexOf(const char *). QVector has no such methods.
>
> But since we do have QListSpecialMethods, we can add inject them into
> QVector too.
Right; I was assuming that would
I facing a discussion like this every couple of months ;)
Yes, we should have a b with accent, cause it is exactly what the
programmer asked QString for; it is not our fault if b with accent is not
what he meant to get after replace.
QString (like any other tool) must not be used blindly or with z
On sábado, 16 de maio de 2020 08:52:19 PDT Arnaud Clère wrote:
> Regarding the relevance of a QUtf8String, I feel like it would not be so
> useful unless it allows to view its content as QChar instead of char (or
> char8_t) since handling multibyte characters is so error prone. At least a
> QChar h
Il 16/05/20 17:52, Arnaud Clère ha scritto:
Regarding the relevance of a QUtf8String, I feel like it would not be so
useful unless it allows to view its content as QChar instead of char (or
char8_t) since handling multibyte characters is so error prone. At least
a QChar handles most unicode cha
Hi all,
As a user, I am happy with simplifications regarding string handling and I
think the choice of utf16 for QString makes sense for most code except for
file/networking code.
I was once concerned about not being able to distinguish between QByteArray
containing utf8 text and QByteArray conta
