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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Aug 24 00:39:47, всего сообщений: 7127
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 1046 из 7127 ====================================== FTSC_PUBLIC =
От   : Nicholas Boel                    1:154/701          09 Jan 14 20:21:02
Кому : Maurice Kinal                                       09 Jan 14 20:21:02
Тема : CHRS kludge implementations
FGHI : area://FTSC_PUBLIC?msgid=1:154/701+52cf5a0f
На   : area://FTSC_PUBLIC?msgid=1:153/7001.0+52cf417e
= Кодировка сообщения определена как: UTF-8 ==================================
Ответ: area://FTSC_PUBLIC?msgid=1:153/7001.0+52cf6a13
==============================================================================
Hello Maurice,

On 10 Jan 14 00:40, Maurice Kinal wrote to Nicholas Boel:

NB>> Hopefully this fixes it. I think I remembered what I did - I cvs
NB>> up'd my Golded+ source and recompiled with iconv support, which
NB>> is experimental. Apparantly it doesn't work very well. :)

MK> It works now ... again.  I am replying to the one that does work but
MK> for the record both 'MSGID: 1:154/701 52cf3786' and 'MSGID: 1:154/701
MK> 52cf394a' are still broken wrt the utf-8 characters being MIA.  Also I
MK> turned the Møøse back on for this area so that it can provide a
MK> check for messages originating from here that have no utf-8 characters
MK> in the message body.  Turns out the Møøse is extremely handy for
MK> this cause.

Yep. Those two messages were while I was unaware of my breakage of Golded+. I
have a feeling whatever that experimental implementation of iconv support was
stripping extended ascii characters. While that may be great for some people,
I enjoy reading messages as they were intended to be written (as much as
possible, anyways).

NB>> Thunderbird still works with it even though the headers are
NB>> usually broken.

MK> That is because the characters in the header don't match the CHRS
MK> kludge.  It is an el-cheapo attempt to cheat the system which is why I
MK> claimed "doomed" in another post.  If they'd have stuck with ascii
MK> only in the headers it would have worked since ascii characters are
MK> legitimate utf-8 characters whereas latin1 characters aren't - or any
MK> other 8-bit characters for that matter.

I'm beginning to wonder if that's something specific to NNTP in general, and
not just Thunderbird. I've been tinkering with slrn for the past day or two,
and while I can set it to read and write using the UTF-8 charset, the NNTP
server(s) I connect to show text/plain 8bit in the headers. :(

I guess I can add that to the other reasons I've never been a big fan of
reading/writing messages via NNTP. While I could probably tinker some more and
possibly get it to work, the interest is fading considerably fast. :)

MK> ... A Møøse once bit my sister ...

Looking good once again!

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
* Origin: Dark Sorrow | darksorrow.us (1:154/701)

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