On Friday September 30 2016 04:29, you wrote to me:
MvdV>> So get the support of some more NCs in R50. To demonstrate MvdV>> there is a demand.
I understand RC50 is asking for just that.
BTW, the ZC2's naming convention for UTF-8 region segments is UTFRxx.
ES> There are too few sysops that supports UTF-8. Mainly because there are ES> no any FTN editors that can natively support multi-byte charsets
A chicken and egg problem. The only FTN software that can do UTF-8 without the use of an external editor is the MBBS package AFAIK. It would be nice if we could get someone to make Golded fully UTF-8 comapatible. If that were to happen, surely more sysop would be interested. And thet would create more demand for UTF-8 capable FTN message editors. Etc..
ES> without so-called «костылей» (crunches).
I think you mean "kludges".
But... now we are talking message editors. This thread started out with the nodelist. And for the nodelist, we do not need to call upon the
In the meantime, lacking a fully UTF-8 version of golded, what I do is that I convert it to the local character set for local use. In my case CP850. For that there is iconv. The R50 sysops could do the same and convert their part of the UTF-8 nodelist back to CP866 for local use. Golded has no problem with compiling a nodelist containing eight bit characters. Ik is a "костылей", but we have to start somewhere.
MvdV>> In the meantime.. why wait for the the top to take action? You MvdV>> could start a "bottum up initiative" by creating an UTF-8 MvdV>> segment for your net and make it available to intersted MvdV>> parties. I am interested in adding UFT5075.nnn to my nodelist MvdV>> compliled for local use.
ES> Just uploaded "utfn5075.274" on your station :)
Got it. Thanks. Now I have to decide what to do with it. ;-) I may ask you for a secure link and regular updates... Stay tuned...
