KK>> If we want for widespread UTF-8 usage in fidonet then we KK>> must fix the lack of unicode-capable editors first. MV> There is something you can do now to promote UTF-8 in Fidonet. MV> You can join the UTF-8 nodelist project. For some time now, ZC2 MV> distributes a UTF-8 version of the nodelist in parallel witg the MV> old ASCII only list.
Through I'm not a big fan of the idea of UTF-8 nodelist project in it's current state because: 1) It is completely separated version of nodelist. So it is prone to out of sync issues with ascii-only version. 2) IMHO it must also contain latin-only representations. Ability to see native representation of information is very good, but to properly understand it you must know that language. If you doesn't know it then you just couldn't read it and most likely couldn't type it. So it renders it basically useless. I understand the desire to keep compatibility with old format but maybe we need to also introduce xml/json version which would contain both ascii and utf-8 representations if they are different.
But despite that why not to join...
MV> So far participation is limited, but it would be a great push for MV> the project if R50 were to join. IIRC RC50 has said that he would MV> join if five NCs in R50 would express the wish to join. (Or was MV> it four?)
MV> NC5075 has already stated he would join and he has an MV> utfn5075.nnn ready for submission. So how about doing some MV> lobbying among your fellow NCs in R50?
Just asked R50C about current state of NC's counter and expressed my desire to join.
--- Claws Mail 3.14.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu) * Origin: Via 2:5019/40 NNTP (GaNJaNET STaTi0N, Smolensk) (2:5019/40.1)
