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


Присутствуют сообщения из эхоконференции UTF-8 с датами от 19 Apr 14 00:41:48 до 01 Apr 24 00:03:00, всего сообщений: 1367
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 1262 из 1367 ============================================ UTF-8 =
От   : Michiel van der Vlist            2:280/5555.1       27 Feb 23 15:12:33
Кому : Rob Swindell                                        27 Feb 23 15:12:33
Тема : codepage
FGHI : area://UTF-8?msgid=2:280/5555.1+63fcba51
На   : area://UTF-8?msgid=317.fidoutf8@1:103/705+286180c2
= Кодировка сообщения определена как: UTF-8 ==================================
Ответ: area://UTF-8?msgid=323.fidoutf8@1:103/705+28628892
Ответ: area://UTF-8?msgid=327.fidoutf8@1:103/705+28667e7f
==============================================================================
Hello Rob,

On Sunday February 26 2023 22:11, you wrote to me:

>> > But oddly enough Synchronat BBS anwers in CP437 when quote replying
>> to an UTF-8 encoded > message...  And this reply is being written using
>> a UTF-8 terminal.

RS> And this reply is being written using a UTF-8 terminal with some
RS> actual non-ASCII characters:

All three of your messages have non-ASCCI charcters. They all have the degree character '°' in the sign off, or whatver you call it. In the last message it is also present in the message test before the "--" (two dashes).

RS> Norco, CA WX: 42.0°F, 79.0% humidity, 0 mph NE wind, 0.15 inches
RS> rain/24hrs

Considering that the CHRS kludge applies to the entire message, I think it is more logical to look at the entire message including header, footer en origin lines to determine the encoding.

Other than that: my comment was on Chris' message that was a quote-reply to my message. He quoted the UTF-8 encoded text but the reply was in CP437 thereby messing up the quote.

Chris seems to have a preference for doing away with "legacy" encodings, so I was a bit surprised that his reply was encoded in CP437 instead of UTF-8.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/5555.1)

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