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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Apr 24 01:17:44, всего сообщений: 7124
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 6530 из 7124 ====================================== FTSC_PUBLIC =
От   : Pavel Gulchouck                  2:463/68           18 Sep 22 17:23:26
Кому : Maurice Kinal                                       18 Sep 22 17:23:26
Тема : FTS-5004
FGHI : area://FTSC_PUBLIC?msgid=2:463/68+63273b43
На   : area://FTSC_PUBLIC?msgid=1:153/7001.2989+6325fc4e
= Кодировка сообщения определена как: CP1125 =================================
Ответ: area://FTSC_PUBLIC?msgid=1:153/7001.2989+632788c1
==============================================================================
Hi Maurice!

17 Sep 22, Maurice Kinal ==> Pavel Gulchouck:

PG>> No FTS, you can just ignore this control.

MK> It turns out that glibc supports CP1125.  I never heard of it before your posts here but it doesn't surprise me any.  The conversion
MK> CP1125 <-> UTF-8 appears to be working 100% so far.  However I don't see any mention of it at IANA;
MK> http://www.iana.org/assignments/character-sets

MK> For the record I am keeping your MSGs as CP1125 and only do the conversions when I quote.  I *NEVER* mess with the originals and
MK> neither does any code here that I am currently using.

PG>> I'll be glad if the FTS about DDN could be improved or corrected.

MK> Understood.  What do you need to make it happen?
MK> I am unsure what the real problem is

Three problems:
1. Disable to add additional information to DDN domain (such as pointlist or fresh network segment).
2. Requirement to skip and ignore addresses like f*.n*.z2.* and any other method built from FTN address from INA when building DDN.
3. Claim that such addresses should not appear in the nodelist even if the domain is not DDN (for example, f*.n*.z*.node.binkp.net or f*n*.z2.dyn.binkp.net).

I proposed changes to the FTS in a message before.

MK> and throwing Russians under the bus isn't going to help ... even if they deserve it.  ;-)

This is not related to the technical problems.
I mentoined this only for explain source of the technical problems (as I think) caused by this FTS.

PG>> And the FTS about charsets too.

MK> Unfortunetly that one might be a tad harder to pull off especially if it isn't listed at IANA.
MK> As I said previously, it is an obscure encoding, or at least it is in this part of the world and without IANA support ... ????

Some codepages listed in the FTS-5003 is not listed at IANA.
For example, cp848 which is not known by glibc or IANA, and I first heard about it from this FTS.

IANA documents related to Internet.
Traditionally on unix systems for russian language before utf-8 as 8-bit encoding used koi8-r, and on dos and os/2 - cp866.
Internet was based on unix, fidonet - on dos (and later os/2). Therefore as primary encoding for russian on Internet was koi8-r, and for fidonet - cp866.
Ukrainian modification of koi8-r is koi8-u (rfc2319), and modification of cp866 is cp1125 (registered as ibm codepage).
IANA documented koi8-u in internet standard, but we in fido should document cp1125 as used in fidonet.

              Lucky carrier,
                           Pavel
                           aka  gul@gul.kiev.ua
--- GoldED+/LNX 1.1.5-b20160827
* Origin: Lucky Carrier BBS (2:463/68)

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