= Сообщение: 1093 из 7127 ====================================== FTSC_PUBLIC = От : Maurice Kinal 1:153/7001 13 Jan 14 03:36:40 Кому : Nicholas Boel 13 Jan 14 03:36:40 Тема : CHRS kludge implementations FGHI : area://FTSC_PUBLIC?msgid=1:153/7001.0+52d35f48 На : area://FTSC_PUBLIC?msgid=1:154/701+52d35b47 = Кодировка сообщения определена как: UTF-8 ================================== ============================================================================== Hey Nicholas!
NB> That's a lot of maybes, though. I'm completely guessing there.
Same situation here. Whatever the real reason for it is, and the lack of documented evidence, anyone here is likely to be guessing, with some guesses being closer to the real mark ... whatever the real mark is or turns out to be if indeed it turns out not to be completely ditched ... which arguably is for the best if that turns out to be what indeed happens.
NB> except possibly the few sysop editors out there
It appears that way. I am in favour of avoiding that happening if at all possible, which so far it appears to be. I'm inclined at this point in time to either have ascii only in headers or stick to whatever the CHRS kludge claims them to be such as the few cp437 messages from Björn where both the header and message Björns were in cp437 rather than the latin-1 Björn in the header with a utf-8 Björn in the message body along with his "CHRS: UTF-8 2" kludge which doesn't match the header Björn encoding but does match the utf-8 Björn in the message body, nevermind what the level 2 thingy is *supposed* to mean seeing as we'd be guessing anyhow.
NB> so I stuck with it and haven't looked back. It really is the best NB> universal charset.
Sounds familiar.
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)
