= Сообщение: 1090 из 7127 ====================================== FTSC_PUBLIC = От : Maurice Kinal 1:153/7001 13 Jan 14 00:58:06 Кому : Nicholas Boel 13 Jan 14 00:58:06 Тема : CHRS kludge implementations FGHI : area://FTSC_PUBLIC?msgid=1:153/7001.0+52d33a1e На : area://FTSC_PUBLIC?msgid=1:154/701+52d3003e = Кодировка сообщения определена как: UTF-8 ================================== Ответ: area://FTSC_PUBLIC?msgid=1:154/701+52d35b47 ============================================================================== Hey Nicholas!
NB> Whether any software actually makes use of it is another story
It doesn't need to in the case of utf-8. utf-8 characters stick out like a sore thumb.
NB> it's supposed to let other software know there are multibyte NB> characters in the header or message
Which other software? If the other software is restricted to 8-bit characters then there isn't anything a level 4 kludge can do to rectify it. They will appear as two 8-bit characters to any application that isn't utf-8 aware. Conversion from utf-8 to whatever 8-bit codepage maybe but then the utf-8 message would have to be restricted to the range of codes that could be successfully converted to the targetted codepage and in that case it should have probably be formatted to that codepage in the first place.
The reason I use utf-8, when I actually put multibyte characters (seldom) in any text based file or whatever I/0, is that there are no real restrictions to any specific range of codes. utf-8 should remain pure methinks. I honestly believe they are more powerful left as is. There is no 8-bit codepage that can compete or make a claim to universality.
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)
