= Сообщение: 331 из 1367 ============================================= UTF-8 = От : Maurice Kinal 1:153/7001 28 Nov 16 11:52:28 Кому : Kees van Eeten 28 Nov 16 11:52:28 Тема : old dutch FGHI : area://UTF-8?msgid=1:153/7001.0+583c1a7c На : area://UTF-8?msgid=2:280/5003.4+583c1036 = Кодировка сообщения определена как: UTF-8 ================================== Ответ: area://UTF-8?msgid=2:280/5003.4+583c2903 ============================================================================== -={ 2016-11-28 12:52:28.437003991+01:00 }=-
Hey Kees!
KvE> I would rather become fluent in the Python language, that KvE> supports UTF natively.
Understood. Personally I have been using bash scripts with assorted other tools (sed, grep, fold) which are far more lean and mean than python, or perl for that matter, which also supports utf-8 and has been in production far longer than python. So far all I've required perl for is it's pack function for converting pkt and msg headers to binary for nodes that subscribe to that mode of operations for messaging. Internally everything messaging here is utf-8 text based and has been since I first started focussing on making utf-8 work for me locally. The same could easily be done with python but to be honest I've been hoping to get rid of perl and NOT replace it with something else just as overbloated and essentially unwanted. I can't see myself using it ever, nevermind for fidonet capable utf-8 messaging. What for?
Since I first encountered python AGES ago I have never found anything appealing about it that I can't achieve with far less resources. Howver I can see it's appeal to MS type hackers given their chosen platform which is most definetly developmentally crippled. Unfortunetly I see that same attitude spreading to linux via lame distributions such as Ubuntu. :::sigh:::
Life is good, Maurice
... Sorg ond slæp somod ætgædre earmne anhogan oft gebindað.