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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Aug 24 00:39:47, всего сообщений: 7127
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 985 из 7127 ======================================= FTSC_PUBLIC =
От   : Maurice Kinal                    1:153/7001         06 Jan 14 19:38:32
Кому : Kees van Eeten                                      06 Jan 14 19:38:32
Тема : all over but the crying?
FGHI : area://FTSC_PUBLIC?msgid=1:153/7001.0+52cb0638
На   : area://FTSC_PUBLIC?msgid=2:280/5003.4+52caf5c9
= Кодировка сообщения определена как: CP866 ==================================
Ответ: area://FTSC_PUBLIC?msgid=2:280/5003.4+52cb2b87
==============================================================================
Hey Kees!

KvE> I also use the kludge for a display routine for e.g. raw packages

That is exactly how I've been using it too.  However most raw pkt's I've seen don't have a CHRS kludge and the encoding is usually 7-bit ascii which doesn't require a CHRS kludge to make themselves known.  Same with UTF-8 characters.  It is *only* the 8-bit characters (ie greater than 0x7f) which require proper identification as to what codepage they correspond to in order to render the intended character.  For this purpose I have been using iconv and it's charmaps in order to display them as utf-8 characters to the terminal application for reading, including things like 'cat', 'less', and the such.  It doesn't *have* to be an editor.  In your case you are limiting yourself to latin-1 characters which won't work with many of the other codepages such as cp866.  It can't be done, not even with Golded+.  That is why I started using a pure utf-8 terminal a few years ago simply because it isn't limited to 8-bit characters.  Also the 8-bit character CP* ones can really cause much grief on an ISO based terminal.  I am sure you have encountered that by now.

KvE> header is in an 8 bit character set

I've noticed that but have sent utf-8 characters in there as well without breaking anything.  You have to be careful not to exceed the string limits though since the character count will be different for 8-bit targetted apps.  For example the Swedish person whose name I won't mention has one character in his name that will appear to be exactly one byte greater than the character count in a utf-8 application.  The strings in FTN apps assume character counts and byte counts to be identical which isn't always true when dealing with utf-8.  The so-called Norwegian utf-8 moose is a good example of this anomalous behavior.  That example is 2 bytes greater than it's character count in a utf-8 app.

KvE> Especially in interesting times

Yes indeed.

Life is good,
Maurice

--- GNU bash, version 4.2.45(2)-release (x86_64-unknown-linux-gnu)
* Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.0)

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