MSGID: 2:5020/12000 4f53923b
REPLY: 2:280/5555 67cecce8
TZUTC: 0300
CHRS: UTF-8 4
Hello Michiel,

orig.message to echo UTF-8 on 10 Mar 25  12:16:07
 MV> There is no generally agreed mechanism to change the encoding in the
 MV> middle of a text file. Is say: don't even try it.

Nodelist is not just text file. It is structured data also. And there is
enought info to set zone/region/network wide information. If we consider
nodelist entries as (in python terminology) 'bytes', that is binary data, we
need this info to make /text/ from these binary strings.

 MV> OK. he message base however is something different. The best may be to
 MV> archive them "as is". Or not, I don't know. But now we are no discussing
 MV> the nodelist.

'Archive as-is' is known to be shortest way from data lake to data swamp) Need
to correctly decode messages creates backpressure against charset-ignoramity.

 MV> I say it is the resposibiliy of the RCs to submit an error free segment to
 MV> the ZC. But let's not make a mauntain out of a mole hil. We have ONE RC
 MV> submitting a segment that causes ONE line in the nodlist to be in error.
 MV> An error that is largely cosmetic.

Thats not mole or pole or something, that's failure at very start.

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