Nil Alexandrov написал(а) к Stas Mishchenkov в Mar 18 09:06:40 по местному времени:

Нello, Stas!

Saturday March 03 2018 23:18, from Stas Mishchenkov -> Michael Dukelsky:

SM> Так, а где почитать за Опус?

OPUS это такая ББСка под ДОС в 80-90х годах была.
Доступно и полезно описано в Вики, там же есть формат сообщений.
http://fileformats.archiveteam.org/wiki/Opus-CBCS

Страничка про Опус есть на НЗ сервере http://www.sentry.org/~trev/opus/
Там есть две полезные ссылки для девелоперов.
1. Message base structures for utility writers for Opus 2.00
http://www.sentry.org/~trev/opus/173files/MSG200.ZIP
2. Opus v1.79 C data structures
http://www.sentry.org/~trev/opus/179files/ostr179.zip

Изначально Опус - это ББС, но ещё заодно сделали её совместимой с фидо.
В последствии, так ещё и круче фидо стало, например цветные менюшки в ББС,
которых раньше не видели, стандарты обмена по модему, файловые запросы и пр.

Формат .msg Опуса не является стандартом FTSC, но на текущий момент, когда
говорят про .msg (husky только Opus понимает, а GoldED имеет выбор, но дефолт
на Opus). Почему в FTSC нет формата Опус? Скорее всего потому, что они
посрались из-за того, кто командует парадом. Какое-то время жил орган IFNA -
International FidoNet Association, но не долго. Опус топили за отсутствие
адинистративного ресурса, за открытось и прозрачность WOC - Worldwide
Opus Consortium.

Я тут ещё скопипастил документ, в котором явно говориться, что time stamp -
это уникальная для Опуса фишечка.

UNIT FIDOFMT;
(%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%)
(% %)
(% %)
(% F I D O M E S S A G E S T R U C T U R E %)
(% %)
(% %)
(%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%)
(%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%)
()
( Opus stores and handles its messages in the traditional )
( FTSC FidoNet message format with the exception that )
( additional dating information is added in a set of two )
( 'timestamp' fields that indicate when a message was )
( created and when it arrived on the system and in the use )
( of certain message flags. The extended use of the flags )
( is done in such a way as to only be of use within the )
( Opus environment and avoidsconflict with other systems )
( which adhere to basic FidoNet standards. )
( In a manner directly descended from the original Fido<tm> )
( BBS system, messages are stored in one or more directories )
( which each correspond to a System Area (topic). )
( Each message is stored in its own file and has a file name )
( format "#.MSG" where "#" is the assigned number of the )
( message. The first messages in any given area would be )
( named 1.MSG, 2.MSG, and so on. )
()
( Each message file consists of a fixed-length header record, )
( immediately followed by a variable-length stream of ASCII )
( text that is terminated by an ASCII NULL (Code 0). )
( All text is considered to be unformatted and continuous )
( without end-of-line sequences unless they are meant to )
( unconditionally force a new paragraph. Traditionally, )
( some message editors and BBS's use a $8D character )
( (CR with 8th bit ON) as a "soft" carriage return. )
( These should be treated as superfluous *unless" they are )
( immediately followed by a space. In that case, the line )
( that the space starts is considered to be fixed format and )
( should not be word wrapped as all other message text will be. )
( The header data contains fixed information about the author, )
( addressee, creation and arrival dates, subject, message )
( numbers that it replies to or is answered by, privacy flags, )
( and so on. In the case of messages in a netmail area, )
( there are many special flags used. )
(----------------------------------------------------------------)


(----------------------------------------------------------------)
( TIME STAMP (Not an FTSC Standard. Unique to Opus) )
(----------------------------------------------------------------)
()
( The following _stamp structure is used in Opus message )
( headers to store a message's creation date (when first )
( written) and the date the message arrived on the system )
( such as when received via netmail. )
()
( This dating information is auxiliary and used by Opus only. )
( It does *not* replace the functionality of the FTSC )
( standard ASCII formatted date field which is also maintained )
( by Opus for compatibility with the rest of the world. )
()
(----------------------------------------------------------------)


Best Regards, Nil
--- GoldED+/LNX 1.1.5