NB> Since my messages are proper UTF-8, it should be a level 4 kludge, NB> according to the FTSC document
Understood. Another obvious flaw in FTSC documentation. No surprise about that here. They still haven't bothered upgrading up to 1989 standards why would the above come as a surprise to anyone? I won't even mention the obsoleted FTN datetime stamp. Not even Microsoft will go out on a limb for that one and they have a shoddy record when it comes to standards, especially ones they claim to support under the guise of 'backwards compatibilty'. What a bad joke that turned out to be eh?
NB> The few times he does post UTF-8 messages
Where? I'd muchly appreciate seeing one.
NB> Unless I use CP866 as my default codepage, his workaround and NB> translation table will not work here.
Oh those Russians! Wait a minute ... he isn't Russian. What kind of operation is he running there?!?!?!?!
Anyhow check your /usr/share/i18n/charmaps directory. There are WAY more supported maps in there than just cp866. I seriously doubt there is any issues there regarding any of the CHRS supported codepages. Sounds to me that his win32 version is seriously handicapped.
NB> or just done for Michiel's version
He can keep it. I think it is a serious mistake. I am sure there are Windows based editors out there that handle utf-8 correctly without having to resort to silliness.
NB> the kludge stuff and/or the necessity of some of it in this one
Agreed. I believe that will ensure topicallity with respect to this particular echo.
Life is good, Maurice
... A Møøse once bit my sister ... --- GNU bash, version 4.2.45(2)-release (x86_64-unknown-linux-gnu) * Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.0)
