On Sun, 3 Mar 2024 22:45:34 +0100, Michiel Van Der Vlist -> Nicholas
Boel wrote:

 MvdV> Yes, they are translated to multi (usually two for most characters used
 MvdV> in Fidonet) byte characters. Only the ASCII characters (0-127) are not
 MvdV> translated and so remain one byte.

Thanks for the explanation. While reading this, I did check the ASCII
table and the characters I'm referring to are all above 127. This also
is kind of reflected while using Golded, if I widen my screen more than
160 characters, less of those lines are wrapped to the next line.

However, it doesn't seem like I can widen my window enough to keep them
all on one line, so I'm guessing when they are translated to utf-8 they
are more than 2 bytes, since I'm well over double the width of an 80
character screen - which the original stat message was made for.

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

 MvdV> To put it simple: if you want to encode CP437 and CP866, you could put
 MvdV> CP437 OR CP866 in the first byte, but you need at least one bit more
 MvdV> information which one it is; CP437 or CP866. That is not exactly how
 MvdV> UTF-8 works but it should give you an idea of why just one byte can not
 MvdV> be enough.

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

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb