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


Присутствуют сообщения из эхоконференции UTF-8 с датами от 19 Apr 14 00:41:48 до 01 Apr 24 00:03:00, всего сообщений: 1367
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 373 из 1367 ============================================= UTF-8 =
От   : Michiel van der Vlist            2:280/5555         26 Dec 16 00:34:23
Кому : Nicholas Boel                                       26 Dec 16 00:34:23
Тема : Merry Christmas
FGHI : area://UTF-8?msgid=2:280/5555+586060c4
На   : area://UTF-8?msgid=1:154/10+585ff045
= Кодировка сообщения определена как: UTF-8 ==================================
Ответ: area://UTF-8?msgid=1:154/10+5860abf1
==============================================================================
Hello Nicholas,

On Sunday December 25 2016 10:08, you wrote to me:

NB> I guess my question would then be, why include printed soft CRs in
NB> messages? Isn't that about as worthless as BOMs?

This soft return thing is a 45+ year old relic from the CP/M era that keeps haunting us till today. In FTS-1 it is documented as a control character which was a mistake that should never have happened. Current practise is and has been for over two decades that it is not a control character but a printable character. In CP437 and CP860 it is the 'i' with accent grave. ì In CP866 it is the characters that looks look 'H' and which is pronounced as 'N' in Russian.

In UTF-8 0x8D can be part of a valid multi byte well formed UTF08 sequence.

In 99.99% of cyber space the soft CR has been extinct for decades, but in Fidonet there unfortunately is still some stone age software around that threats it as a control character and it can not be persuaded not to do so. Telegard comes to mind. As you have already discovered Golded can be taught to do it right. Some tossers also have a configuration option to strip or not strip soft returns.

Anyway, for proper UTF-8 support all software should be configured to not treat 0x8D as a control character. And if it can not be configured that way, it should be nominated for the Darwin Award...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Blijf Tønijn (2:280/5555)

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