Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    UTF-8    |    UTF-8 encoded messages    |    382 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 281 of 382    |
|    Sergey Dorofeev to Michiel van der Vlist    |
|    UTF-8 nodelist report    |
|    10 Mar 25 03:07:17    |
      MSGID: 2:5020/12000 4f539214       REPLY: 2:280/5555 67cd7088       TZUTC: 0300       CHRS: UTF-8 4       Hello Michiel,              orig.message to echo UTF-8 on 09 Mar 25 11:42:16        MV> The encoding for the regular nodelist IS defined: ASCII and ASCII only.        MV> For backward compatibility it must stay that way. There still may be        MV> nodelist processing software around that breaks when he highest bit is not        MV> zero. That is why MakeNl (without the ALLOW8BIT setting) substitutes a        MV> question mark for characters with the highest bit set.              About question mark, is it valid symbol for sysop name? Can somebody name       himself as "???? ???? ????" for example?               MV> Very bad idea. Having more than one encoding within the same file is a bad        MV> idea anyway, not just for the nodelist but for ANY text file.              Agree, thought it is technically possible, but it will kill 99% programmers.               MV> Are you serious? You really still want every back alley in Fidonet to have        MV> its own 8 bit encoding? With all the forward and backward re-encoding and        MV> other limitations? C'mon.. That's chaos! Unicode was invented for the very        MV> purpose of getting rid of all this codepage shit.              That's the thing that I do to keep all messages on my node in UTF-8... without       stable success though.               MV> Why do you think Microsoft went full Unicode internally? Three decades        MV> ago. Why do you think 99% of what is on the web is UTF-8? To get rid of        MV> the mess of all the hundreds of 8 bit encodings that floated around!              There was two ways... make encoding a part of type, as if you use int for       range, how to know, is it in miles or kilometers... or set the one and only       encoding.       Second way was chosen.               MV> Nah, as far as the nodelist goes, it is either just ASCII or UTF-8. No        MV> more codepage shit.              May be it is duty of ZC, to drop invalid segment, and not "help" sysop to       publish errors, replacing them with any mark.              Sergey              ... vim       --- PyFTN        * Origin: fluid.fidoman.ru (2:5020/12000)       SEEN-BY: 4/0 50/109 90/0 105/81 106/201 128/187 153/757 7715 154/10       SEEN-BY: 154/110 218/700 840 221/1 6 360 226/30 227/114 229/110 114       SEEN-BY: 229/317 426 428 470 700 705 280/464 291/111 301/1 320/219       SEEN-BY: 335/364 341/66 234 900/0 902/0 26 905/0 5015/46 5020/715       SEEN-BY: 5020/830 848 1042 2065 4441 12000 5030/49 1081 1474 5058/104       SEEN-BY: 5061/133 5097/31       PATH: 5020/12000 4441 1042 221/6 341/66 902/26 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca