On 25/01/2020 11:18 a.m., Michiel van der Vlist wrote:
MvdV> If looks OK if you view it with a viewer configured for UTF-8.
Ah.. yes. I was taking things for granted here and using a couple of
rudimentary DOS/Win text editors to view the raw nodelist at first. But
Notepad++ and Texmaker are much better and provide charset changes.
MvdV> Let me explain.
MvdV> 1) For $reasons Bjorn does not participate..
MvdV> 2) He nevertheless insists..
MvdV> 3) He also insists that every sysop should..
[snippity snip snip]
Thanks. I have to process that for a little while before I put my
/other/ foot in my mouth. LOL
MvdV> 4) For regions participating in the UTF-8 nodelist project the
MvdV> procedure is as follows:
[snip]
Sounds simple enough. Maybe I'll dare to ask some more stupid
questions. LOL
If the rule/policy is ASCII for the standard nodelist (and according to
FTSC-0005 it appears to be so), then clearly the 2:203/208 is invalid
and should be stripped from publication until corrected. ? Simple.
MvdV> 8) The line for 2:2/2 is not derived from a file submitted by
MvdV> the RC, but originates directly from the ZCs system. Therefore
MvdV> this line contains proper UTF-8.
Nice. That is good!
MvdV> I hope this clearifies things...
It has. I appreciate it!
--
Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc
--- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
|