Subj : UTF-8 nodelist report
To : Michiel van der Vlist
From : Sergey Dorofeev
Date : Fri Mar 07 2025 03:01 pm
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)
