Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    GOLDED    |    GoldED Public Release discussion.    |    2,690 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,232 of 2,690    |
|    Nicholas Boel to Michiel van der Vlist    |
|    Need volonteers to test another patch    |
|    03 Mar 24 10:33:12    |
      MSGID: 1:154/10 65e4a646       REPLY: 2:280/5555 65e49e05       PID: Smapinntpd/Linux 2.0 b20240302       TZUTC: -0600       TID: hpt/lnx 1.9 2024-02-05       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        * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)       SEEN-BY: 15/0 18/200 90/1 103/705 105/81 106/201 120/616 123/10 124/5016       SEEN-BY: 128/260 129/305 135/225 153/757 7715 154/10 30 40 50 700       SEEN-BY: 203/0 218/700 220/90 221/0 6 226/18 30 227/114 229/110 112       SEEN-BY: 229/113 206 307 317 400 426 428 470 664 700 240/1120 5832       SEEN-BY: 266/512 280/464 5003 5555 282/1038 291/111 292/854 8125 301/1       SEEN-BY: 310/31 320/219 322/757 341/66 234 342/200 396/45 423/120       SEEN-BY: 460/16 58 256 1124 5858 467/888 633/280 712/848 770/1 2320/105       SEEN-BY: 3634/12 5020/400 1042 5054/30       PATH: 154/10 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca