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)
|
