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,236 of 2,690    |
|    Vitaliy Aksyonov to Michiel van der Vlist    |
|    Re: Need volonteers to test another patc    |
|    03 Mar 24 16:31:50    |
      REPLY: 2:280/5555 65e4ee8f       MSGID: 1:104/117 65e50984       CHRS: US-ASCII 2       TZUTC: -0700       TID: hpt/lnx 1.9 2022-07-03       Hello Michiel.              03 Mar 24 22:31, you wrote to Nicholas Boel:               NB>> So, at this point it's basically working and displaying properly,        NB>> but then comes in the 'characters' vs 'bytes' thing that Golded        NB>> isn't supporting, so it is wrapping what it thinks is double,        NB>> triple, or even quadruple the amount of 'characters' that are        NB>> there.               MvdV> When it comes to mapping the number of characters to the number of        MvdV> bytes, when you look at the UTF-8 encoding table, about two screens        MvdV> down here:               MvdV> https://en.wikipedia.org/wiki/UTF-8               MvdV> You can see that the length of the byte sequence can be determined        MvdV> just by looking at the first byte. Look from bit 7 to the right. The        MvdV> number of '1' bits equals the number of bytes in the character. All        MvdV> the follow up bytes start with '10'. So to get the number of        MvdV> characters ignore the bytes starting with '10' when counting the        MvdV> bytes.               MvdV> Breaking a line should only occur /before/ a byte starting with '0' or        MvdV> '11'.               MvdV> Knowing all that it should be doable to let Golded display properly.               MvdV> Perhaps the best strategy is to have Golded alway use UTF-8        MvdV> internally. Almost everyone else does these days...              That would be perfect. It only takes huge amount of effort. Especially with       keeping code backward compatible with systems, which may not have Unicode       support. I keep thinking about it and looking for possible ways to implement.              For now I'd be happy to make iconv work properly. In this case GoldEd user may       get rid of most (if not all) of translation tables. The problem is that source       code has huge amounts of duplicated code and sometimes functions and variables       names say nothing about what do they do. I spend huge amount of time just to       understand what's going on.              For example function, which splits message to lines is almost 1000 lines long!       It has variables, used in multiple places, it not only splits the message, but       guess charset, do recoding and other fun stuff.              Vitaliy              --- GoldED+/LNX 1.1.5-b20240223        * Origin: Aurora, Colorado (1:104/117)       SEEN-BY: 15/0 18/200 50/109 90/1 104/117 105/81 106/201 128/260 129/305       SEEN-BY: 135/225 153/7715 218/700 226/30 227/114 229/110 112 113 206       SEEN-BY: 229/307 317 400 426 428 470 664 700 266/512 280/464 5555       SEEN-BY: 282/1038 291/111 292/854 301/1 320/219 322/757 342/200 396/45       SEEN-BY: 460/16 58 256 1124 5858 463/68 467/888 633/280 712/848 3634/12       SEEN-BY: 5000/111 5001/100 5005/49 5015/46 5020/828 846 1042 4441       SEEN-BY: 5030/49 5054/8 30 5061/133 5075/128 5083/444 5090/958       PATH: 104/117 5020/1042 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca