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


Присутствуют сообщения из эхоконференции UTF-8 с датами от 19 Apr 14 00:41:48 до 22 Mar 24 00:15:07, всего сообщений: 1365
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 411 из 1365 ============================================= UTF-8 =
От   : Konstantin Kuzov                 2:5019/40          27 Feb 17 22:32:00
Кому : Maurice Kinal                                       27 Feb 17 22:32:00
Тема : Is Synchronet UTF8 Ready?
FGHI : area://UTF-8?msgid=2:5019/40+58b47eb3
На   : area://UTF-8?msgid=1:153/7001+58b4664f
= Кодировка сообщения определена как: CP866 ==================================
Ответ: area://UTF-8?msgid=1:153/7001+58b4847d
==============================================================================
Konnichi wa, *Maurice-kun*! Aogu manako oyobi uketamawaru waga koe!
Tomodachi _Maurice Kinal_ tsukuru airon _Konstantin Kuzov_
Nichiji - /*27 Фев 17 17:47*/, Daizai - /*Is Synchronet UTF8 Ready?*/:

KK>> Actually, his CHRS kludge is perfectly valid.

MK> But does it matter?

Yes it is. This is the only reliable source of actual used codepage.

MK> Is there any way to verify it being accurate? For example if I claim
MK> CP866 characters in my message by adding a CHRS that claims it, how do
MK> you or anyone else confirm that it indeed contains CP866 and not some
MK> other 8 bit codes?

It doesn't need to be verified in any way. If presented kludge doesn't match actual used codepage then writer of that message hasn't configured his editor right.

KK>> So don't be surprised when they turns to complete garbage because
KK>> heuristic detection makes a mistake.

MK> That is never the problem with actual utf-8 text.  The problem is when
MK> an inferior editor quotes them back.

The point is: if you doesn't present codepage information then recepient may see an incorrectly decoded message despite the fact that his editor supports unicode. Assumption that any message without CHRS kludge is UTF-8 by default is completely wrong, especially in fidonet where dominating codepage is CP866. And you can't rely completely on hereustic analysis algorithms as they all have margin of error.

I had written about that in this echo in the past:
area://UTF-8?msgid=2:5019/40+53b49cb9

My position didn't changed since then:
=== QUOTE ===
if anyone write message with bogus or absent CHRS kludge then he is enemy to himself! Recepients can't reliable identify codepage in automatic mode. So, possibly they can't read this message at all, not because their soft is outdated and not supporting this codepage, but because author of the message don't indicate what codepage he is actually writing in and software isn't smart enough to successfully guess.
=== QUOTE ===

Ganbatte, *Maurice*!

[_N0SF3R@TU_]
... GoldED-NSF/LNX 1.1.5-b20140107 (Linux 3.19.1-gentoo iF6M42)
--- #[Kaori Sekken: Master.NoSFeRaTU[@]Gmail.com] [Kumi Nyaa]#
* Origin: Ojisan, oriru mottekuru suna oyobi korosu sagaru kabe (2:5019/40)

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