Il 11/06/24 07:12, Thiago Macieira ha scritto:
>> I'd like to know how much breakage this solution or mine would imply.
Marc Mutz (11 June 2024 21:44) replied:
> I may have missed something, but I still can't see what your solution
> is? I've enumerated the options, would you be so kind as to poin
Nope just TWO code points e.g. U+1F1FA: REGIONAL INDICATOR SYMBOL LETTER U)
followed by 🇸 (U+1F1F8: REGIONAL INDICATOR SYMBOL LETTER S) for the US flag,
-Original Message-
From: Development On Behalf Of Giuseppe
D'Angelo via Development
Sent: 11 June 2024 20:09
To: development@qt-proje
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).
Giuseppe D'Angelo (11 June 2024 20:09) replied
>> Th
On 12/06/2024 10:51, Edward Welbourne wrote:
I'll trust Peppe's count is thus of bytes in UTF-8.
No, it's 7 code *points*. Regional flags have a complicated encoding
scheme. Wales' flag is encoded as:
U+1F3F4 WAVING BLACK FLAG
U+E0067 TAG LATIN SMALL LETTER G
U+E0062 TAG LATIN SMALL LETTER B
That's not the current encoding scheme for *national* flags.
The flag for Wales if done using "regional flag encoding" based on modifiers to
"Waving black flag" (U+1F3F4) which I agree can have up to seven but in any
case, the critical point we agree on is the > 1 byte issue...
D.
-Origina
On Tuesday 11 June 2024 12:44:11 GMT-7 Marc Mutz via Development wrote:
> 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 some
