Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции UTF-8
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции UTF-8 с датами от 19 Apr 14 00:41:48 до 29 Mar 24 00:14:49, всего сообщений: 1366
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 430 из 1366 ============================================= UTF-8 =
От   : Konstantin Kuzov                 2:5019/40.1        01 Mar 17 14:14:54
Кому : Maurice Kinal                                       01 Mar 17 14:14:54
Тема : Re: it is all greek to me
FGHI : area://UTF-8?msgid=2:5019/40.1+58b6ad2a
На   : area://UTF-8?msgid=1:153/7001+58b5840d
= Кодировка сообщения определена как: UTF-8 ==================================
==============================================================================
Greetings, Maurice!

MK> Thank you.  Actually it was easy and did no harm to anything that really
MK> matters.  I just slightly modified a bit of abandoware code I happen to
MK> have handy.  I used that same code to generate all the goofy
MK> 'demonstrate' messages.

All those 'demonstrate' messages do are demonstrating your ignorance and nothing else.

MK> The only one I missed was a CP437 one which the sysops here in
MK> North America have been deluded into thinking is the norm,

And why it isn't?

MK> although some call it IBMPC.

Yes, technically IBMPC is CP437 if there are no CODEPAGE kludge. In reality on contrary even in Russian echoes there are messages with CHRS IBMPC but without CODEPAGE whose actually written in CP866.
But that's all just a legacy stuff and must not be presented in new messages for at least a few decades. Today all that legacy can be just ignored by editors as it is most likely not represent actually used codepage anyway.

KK>> Or if you have just specified "CHRS: CP737 2" then all "magically"
KK>> worked as is...
MK> Really?  I seriously doubt that given that it isn't a supported
MK> encoding.  Mind you that doesn't REALLY matter ... does it?  ;-)

Supported by what? For example it is supported on my end, actually my current client supports all encodings whose iconv understand.
If you mean that it isn't specified in FTSC-5003 then you are wrong. FTSC-5003 just specify most commonly used codepages and not restrict you to only specified codepages. You can write you messages in whatever codepage you want, but you must supply CHRS kludge to indicate what codepage was used. It just a common sense to don't use anything rare because there are no guarantee that it can be read and understood by receivers.

--- Claws Mail 3.14.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
* Origin: Via 2:5019/40 NNTP (GaNJaNET STaTi0N, Smolensk) (2:5019/40.1)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.013918 секунды