KE> I have been looking into Romanisation of Cyrillic names. Indeed KE> there are a number of standards. Just to make a start, I looked at KE> the ICAO tranlation, that is used to translate Cyrillic names to KE> Latin for use in machine readable passports. KE> The is some Perl code to do the translation from Cyrillic to KE> Latin. I tried a reverse routine, that is not complete yet, ad it KE> probably does a dusgusting translation, but at lest the same comes KE> out when translated back to Latin. A norn for Fidonet could be to KE> use the ICAO method for the nodelist as well.
Sysops already provided their latin names representation, forcing them to any auto transliteration script isn't a wise move. It can lead to frustration and even anger from sysops whose names suddenly changed without their request. If that thing takes off then I'll just setup a table in database and will store both representations there. Then just generate both versions from that database.
KK>> I hardly imagine a man who in 2017 doesn't know latin KK>> alphabet on transliteration level. But easily imagine the KK>> one who doesn't know cyrillic alphabet. I don't even say KK>> anything about any asian languages or for example hebrew. KE> Lets take it one step at a time. There are very few participants KE> in Fidonet that require Asian languages. Cyrillic is difficult KE> enough with the difference between Russia, Ukrain, en Belarusse. KE> As for hebrew, all sysops in R40 are of Russian origin.
Lets not assume anything based on current population situation. It is a point of UTF-8 nodelist thing to have virtually any alphabet isn't it? Maybe tomorrow there will be plenty of chinese friends there, who knows? And they will be dealing with the crippled legacy not better than we currently have. Ability to read any information is important. And English language as the "global" language is the best suited for that.
KK>> Yes, so as I suggested above we can use ASCII version as a KK>> source for "extended" unicode version. And virtually nothing KK>> prevents generation of additional versions with different KK>> format. KVE> It is far easier to degrade an extended version, that it is to KVE> enrich a limited one.
Maybe, but as Michael mentioned ascii-only version won't go anywhere. I think currently it's virtually impossible to change segments format and to convince Ward to change his software to produce various versions of nodelist from that one source. So the only way we can go for now is building utf-8 versions from ascii-only nodelist and extend it with additional information if wouldn't want to deal with out of sync issues. Maybe in distant future we can swap them to how it must be - building a limited version from extended one. But we are not there yet.
--- 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)
