Subj : Re: Is Synchronet UTF8 Ready? To : Konstantin Kuzov From : Maurice Kinal Date : Tue Feb 28 2017 21:46:51 -={ 2017-02-28 21:46:51.486953722+00:00 }=- Hey Konstantin! KK> Extremely Naive Charset Analyser GIT: KK> [+] Charset: UTF-8 ------------------- :r !enca --version starts enca 1.20-dev Features: -librecode-interface +iconv-interface +external-converter +language-detection -locale-alias +target-charset-auto +ENCAOPT Copyright (C) 2000-2005 David Necas (Yeti) (), 2005 Zuxy Meng (). Enca is free software; it can be copied and/or modified under the terms of version 2 of GNU General Public License, run `enca --license' to see the full license text. There is NO WARRANTY; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ------------------- :r !enca --version ends For the message I am replying to, "MSGID: 2:5019/40.1 58b5732e", piped to 'enca -L none -' it reports; Universal transformation format 8 bits; UTF-8 which is correct. However if I convert it to either KOI8-R, CP1251, ISO-8859-5 or CP866 then I have to specify the language "-L russian" for it to correctly identify the encoding. It did get it correct in all cases whereas file only identified it correctly when it is UTF-8 encoded but does properly identify it as 8 bit characters no matter which of KOI8-R, CP1251, ISO-8859-5 or CP866 was deployed. Interesting. Life is good, Maurice .... Sibb æfre ne mæg wiht onwendan, þam ðe wel þenceð. Kinship can never in any way be set aside, for one who thinks rightly. --- GNU bash, version 4.4.12(1)-release (x86_64-atom-linux-gnu) * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001) .