= Сообщение: 1119 из 7127 ====================================== FTSC_PUBLIC = От : Maurice Kinal 1:153/7001 15 Jan 14 18:47:34 Кому : Björn Felten 15 Jan 14 18:47:34 Тема : CHRS kludge implementations FGHI : area://FTSC_PUBLIC?msgid=1:153/7001.0+52d6d7c6 На : area://FTSC_PUBLIC?msgid=2:203/2+52d66224 = Кодировка сообщения определена как: UTF-8 ================================== ============================================================================== Hey Björn!
BF> Well, the problem is within T-bird
Could be. I am guessing that the problem with this one is whatever added the latin1 Björn to the header but retained the utf-8 Björn in your quote of my reply to mark. If indeed it is the level 2 thingy that is doing that then it makes even more sense to ditch it in the case of utf-8 messaging. It worked fine as long as your characters are all indeed 8-bit, CP437 in "MSGID: 2:203/2 52d6601c". Either that or ascii only in the headers which would be the simplest fix.
I do it right simply because I leave well enough alone and if characters are utf-8 they stay utf-8. Everything else is ascii. I don't bother with the entire CHRS kludge and the only reason I could fix the Björn in the header from "MSGID: 2:203/2 52d66224" (the one I am replying to) has nothing to do with levels but simply because I know what it is supposed to be and not because of the "CHRS: UTF-8 2" kludge. I know that latin1 characters are *NOT* utf-8 characters despite the fact that some editors can be configured to remap them to utf-8 characters.
ASCII only headers is the simplest fix although I'd rather see UTF-8 messaging remain purely UTF-8 including headers.
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)
