Hello Björn!

19 Feb 15 00:11, you wrote to me:

 BF>    That was the idea when the allow8bit function was recently added to the
 BF> MakeNl program. A function that I added (or rather a US restriction that I
 BF> removed) already in 1999 in my Y2K patched version.

 In my local copy of makenl I bremoved the restriction of 7 bits, before it
 made it into the code.

 BF>    If no FTN software is broken, why insist on a ban that could have
 BF> been lifted more than 15 years ago?

 It is useless to regurgitate a subject for 15 Years, without coming up
 with solutions for the real problem.

 It still does not remove the question, which encoding should be used.

 Skipping ahead to a solution, that suits nobody is not a sign of vision, but
 of the lack thereoff.

 Be happy that there is an attempt to a parrallel nodelist, so those who have
 it in their capabillities, can start to build the bridges for a posssible
 use in the future.  UTF-8 supporting fidonet software will not just fall
 out of the blue and 100% adoption will not happen in our lifetime.

 If you are so eager, that some progress is made, I have not seen any changes
 in the preliminary list that Ward produced, that indicate to the submission
 of a utfr20.xxx.

Kees

--- GoldED+/LNX 1.1.5