On Tuesday 11 June 2024 13:03:11 GMT-7 Volker Hilsheimer via Development
wrote:
> Also, if the character value is outside the US-ASCII range, then the only
> alternative would be to interpret it as an incomplete UTF-8 sequence, which
> can’t be the right answer. QString::arg(char) (or operator+(ch
On Tuesday 11 June 2024 12:08:45 GMT-7 Giuseppe D'Angelo via Development
wrote:
> Il 11/06/24 07:12, Thiago Macieira ha scritto:
> > I'm arguing that such code is likely already broken (producing mojibake)
> > for
> > non-US-ASCII content, so having U+FFFD instead of mojibake is not
> > worse. Yo
On Tuesday 11 June 2024 12:09:17 GMT-7 Giuseppe D'Angelo via Development
wrote:
> And it's not 2. 🏴 is 7 code points.
And that requires 4 code units (bytes) per code point in UTF-8, for a total of
28 bytes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel
> On 11 Jun 2024, at 21:08, Giuseppe D'Angelo via Development
> wrote:
>
> Il 11/06/24 07:12, Thiago Macieira ha scritto:
>> I'm arguing that such code is likely already broken (producing mojibake) for
>> non-US-ASCII content, so having U+FFFD instead of mojibake is not worse. You
>> wouldn't be
On 11.06.24 21:08, Giuseppe D'Angelo via Development wrote:
> Il 11/06/24 07:12, Thiago Macieira ha scritto:
[...]
> > I'd like to know how much breakage this solution or mine would imply.
I may have missed something, but I still can't see what your solution
is? I've enumerated the options, would
Il 11/06/24 11:36, David C. Partridge ha scritto:
Anyone iterating bytewise over a char[] in UTF-8 has also got serious
bugs given that a UTF-8 "graphic character" can be up to 8 bytes
(national flags comprise two UTF-8 code points).
There's no such thing as a UTF-8 "graphic character". Graphem
Il 11/06/24 07:12, Thiago Macieira ha scritto:
I'm arguing that such code is likely already broken (producing mojibake) for
non-US-ASCII content, so having U+FFFD instead of mojibake is not worse. You
wouldn't be able to work around the issue by un-doing the improper encoding,
which means it woul
Hi!
Here is Qt 6.7.2 release note draft:
https://codereview.qt-project.org/c/qt/qtreleasenotes/+/567597
Please review it asap; we need to finalize it before official release which is
planned to be happen this Friday (14th June)
br,
Jani
--
Development mailing list
Development@qt-project.org
h
Anyone iterating bytewise over a char[] in UTF-8 has also got serious bugs
given that a UTF-8 "graphic character" can be up to 8 bytes (national flags
comprise two UTF-8 code points).
David
-Original Message-
From: Development On Behalf Of Thiago
Macieira
Sent: 10 June 2024 22:14
To:
Hi Fabian,
Am 10.06.2024 um 16:37 schrieb Fabian Kosmale:
there has been no further development on making
QObjectBindableProperty public, or much work at all when it comes to
extending bindable properties and their usage inside Qt. The most
substantial feature was an external contribution to sup
10 matches
Mail list logo
