TID: FMail-W32 2.2.0.0
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 4
MSGID: 2:280/5555 65e4ee8f
REPLY: 1:154/10 65e4a646
Hello Nicholas,

On Sunday March 03 2024 10:33, you wrote to me:

 NB> So, at this point it's basically working and displaying properly, but
 NB> then comes in the 'characters' vs 'bytes' thing that Golded isn't
 NB> supporting, so it is wrapping what it thinks is double, triple, or
 NB> even quadruple the amount of 'characters' that are there.

When it comes to mapping the number of characters to the number of bytes, when
you look at the  UTF-8 encoding table, about two screens down here:

https://en.wikipedia.org/wiki/UTF-8

You can see that the length of the byte sequence can be determined just by
looking at the first byte. Look from bit 7 to the right. The number of '1'
bits equals the number of bytes in the character. All the follow up bytes
start with '10'. So to get the number of characters ignore the bytes starting
with '10' when counting the bytes.

Breaking a line should only occur /before/ a byte starting with '0' or '11'.

Knowing all that it should be doable to let Golded display properly.

Perhaps the best strategy is to have Golded alway use UTF-8 internally. Almost
everyone else does these days...

 NB> Thank you for the explanation. This definitely helps me to understand
 NB> what is happening.

You'r welcome.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: Nieuw Schnøørd (2:280/5555)
SEEN-BY: 15/0 18/200 90/1 103/705 105/81 106/201 124/5016 128/260
SEEN-BY: 129/305 135/225 153/757 7715 154/10 30 203/0 218/700 221/0
SEEN-BY: 221/6 226/30 227/114 229/110 112 113 206 307 317 400 426
SEEN-BY: 229/428 470 664 700 240/1120 5832 266/512 280/464 5003 5555
SEEN-BY: 282/1038 291/111 292/854 8125 301/1 310/31 320/219 322/757
SEEN-BY: 341/66 234 342/200 396/45 423/120 460/16 58 256 1124 5858
SEEN-BY: 467/888 633/280 712/848 770/1 5019/40 5020/400 1042 5053/58
SEEN-BY: 5054/30 5075/35
PATH: 280/5555 464 460/58 229/426