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

orig.message to echo UTF-8 on 07 Mar 25  09:36:19
 MV> He insists on entering the 'a' and 'o' with umlaut in Säve and Björn in
 MV> 202/208 in Latin-1 in the normal ASCII nodelist. So in the ASCII list they
 MV> are replaced by question marks by MakeNl. In the UTF list which in his
 MV> case is just a copy of the ASCII segment submitted, they appear "as
 MV> submitted" and the line is flagged as in error by my program.

I think it is not very contradictory. I he will success in entering non-ASCII
chars in nodelist (making it full 8-bit), encoding must be defined. Ok, if it
will be latin-1, but let it be only for European segments.
That is, lets define encoding on per-region or even per-network basis. So when
importing nodelist, it must be split back on segments and correctly transcoded.
E.g. default encoding if ASCII, so Zone records must be ASCII. But zone may
specify own encoding, so regions in it may use it in own record, and define
encoding for underlying regions. Further, region record use zone encoding, and
may define encoding for networks. Network record use region encoding and may
define encoding for node records.

 MV> To get it right Björn would have to be convinced to let go of the idea
 MV> that entering LATIN-1 in the regular nodelist is not a good idea. Plus
 MV> that he would have to start participating in the UTF nodelist project.

Usage of latin-1 has the issue, as it is windows' encoding, but in FIDO
traditionally used DOS charset such as CP437 (IBMPC), CP850, CP866.

 MV> I have tried and sort of given up... :-(

If encoding for defaut nodelist will be settled, there will be no issue to
transcode it to UTF-8.

Sergey

... vim
--- PyFTN
 * Origin: fluid.fidoman.ru (2:5020/12000)
SEEN-BY: 1/19 16/0 19/37 50/109 105/81 106/201 123/130 128/187 142/104
SEEN-BY: 153/7715 154/110 203/0 218/700 221/1 6 242 226/30 227/114
SEEN-BY: 229/110 114 317 426 428 470 700 705 230/0 240/5832 280/464
SEEN-BY: 280/5003 291/111 292/854 301/1 113 812 320/119 219 319 2119
SEEN-BY: 322/762 341/66 423/81 902/26 5015/46 5020/715 830 848 1042
SEEN-BY: 5020/2065 4441 12000 5030/49 1081 1474 5058/104 5061/133
SEEN-BY: 5097/31
PATH: 5020/12000 4441 1042 301/1 221/1 320/219 229/426