Commit ad25dd53 authored by Kent Engström's avatar Kent Engström

corrected some spelling errors; changed cross-references so that new

versions of makeinfo will stop complaining; added forbid-secret to the
list of conference flags above the table.
parent e5a4a4b0
......@@ -2,7 +2,7 @@
@c
@c FIXME: Explain how the garb works with nice and keep-commented
@c
@c $Id: Protocol-A.texi,v 1.82 1999/07/02 00:12:55 byers Exp $
@c $Id: Protocol-A.texi,v 1.83 1999/07/07 07:44:16 kent Exp $
@c %**start of header
@setfilename protocol-a.info
@settitle LysKOM Protocol A
......@@ -245,7 +245,7 @@ The following calls have change status from Experimental to Recommended.
@item 78=get-uconf-stat
@end itemize
The following calls are have changed status from Recommended or
The following calls have changed status from Recommended or
Experimental to Obsolete.
@itemize @bullet
......@@ -293,11 +293,11 @@ use 80=accept-async to listen to 15=async-new-text instead.
@item Notes
@itemize @bullet
@item Since protocol version 9 setting a priority of zero in a
@item Since protocol version 9 setting a priority of zero for a
conference was supposed to indicate passive membership in a conference.
It was largely up to the client to implement this. True passive
memberships have been introduced in this protocol version through the
Membership-type extension to Membership type. In order to maintain
Membership-type extension to the Membership type. In order to maintain
compatibility with clients that interpret priority 0 as passive
membership, the old calls @pxref{add-member-old} and
@pxref{get-membership-old} perform magic, translating between priorities
......@@ -553,7 +553,8 @@ possible since it places a much smaller load on the LysKOM server.
Each conference has a type, which is essentially a collection of boolean
flags. Currently the flags @code{rd-prot}, @code{letterbox},
@code{secret}, @code{original} and @code{allow-anonymous} are defined.
@code{secret}, @code{original}, @code{allow-anonymous} and
@code{forbid-secret} are defined.
@table @code
@item rd-prot
......@@ -572,7 +573,7 @@ with the person name. It is currently not possible to explicitly set or
clear this flag on a conference.
@item secret
Conferences of this type are secret. The server will not divulge any
information of the existence of the conference to persons who are not
information about the existence of the conference to persons who are not
members or supervisors of the conference. If a mailbox is made secret,
that person cannot log in using the person name, but must specify a
person number instead.
......@@ -678,18 +679,18 @@ created. It is the time when the CC recipient was added.
The blank carbon-copy recipient group is identical to the carbon-copy
recipient group above. The difference is the visibility of the
information. A carbon-copy recipient group is visible to anyone that is
allowed to fetch both the text status of the involed text and the
allowed to fetch both the text status of the involved text and the
conference status of the involved conference. (That is, as long as the
conference isn't secret everybody is allowed to se the carbon-copy
conference isn't secret everybody is allowed to see the carbon-copy
recipient group.)
A BCC recipient group is only visible to members and supervisors of the
recipient. This is enforced by the server.
This type of group was introduced in protocol version 10. When
old-style calls such as @xref{get-text-stat-old} are used this
will be converted to a CC recipient group by the server for the benefit
of clients that don't understand this group.
old-style calls such as get-text-stat-old (@pxref{get-text-stat-old})
are used this will be converted to a CC recipient group by the server
for the benefit of clients that don't understand this group.
@table @code
@item bcc-recpt
......@@ -724,7 +725,7 @@ the author, after the article had been created. It contains the person
number of the person who added the article as a comment.
@item sent-at
Present when the article was added as a comment after the article had
been created. It contains the time when is was added as a comment.
been created. It contains the time when it was added as a comment.
@end table
......@@ -735,7 +736,7 @@ been created. It contains the time when is was added as a comment.
Always present when the article is a footnote to another article.
@item sent-at
Present when the article was added as a footnote after the article had
been created. It contains the time when is was added as a footnote.
been created. It contains the time when it was added as a footnote.
@end table
......@@ -813,7 +814,7 @@ these definitions will be made backwards-compatible, if possible.
Creation and deletion of items with a predefined type can cause
arbitrarily complex and wonderous behavior in the server. Furthermore,
the server may place constraints on the items with regard to content,
flags, who can create them, to what objects they can be attached to and
flags, who can create them, to what objects they can be attached and
so forth. The server may also silently enforce specific values for any
field of an item, regardless of what the client requests.
......@@ -1094,7 +1095,7 @@ the there is a match (negative filter), even if one of the filter allowed it. E
@item mx-reject-forward [26] (conference)
Data is a string with either an email name on the same format as
aux-info rediret [8]. The mail is forwarded to this address if it was
aux-info redirect [8]. The mail is forwarded to this address if it was
rejected by "mx-import-filter".
@item notify-comments [27] (letterbox)
......@@ -1743,9 +1744,9 @@ Aux-Item and Aux-Item-Input have the following meaning:
The number of the item within the list where it is found. This number
together with a conference or text number uniquely identifies a
particular aux-item. (There is also a global list of Aux-Items for the
server. That list is manipulated via the @xref{modify-system-info}
request, and when using that request the aux-no is enough to uniquely
identify the aux-item.)
server. That list is manipulated via the modify-system-info
(@pxref{modify-system-info}) request, and when using that request the
aux-no is enough to uniquely identify the aux-item.)
This field is not present in @code{Aux-Item-Input}. It is assigned by
the server.
......@@ -5224,7 +5225,7 @@ person's membership list.
( Text-List );
@end example
This call is obsolete; @xref{map-created-texts} should be used instead.
This call is obsolete; instead you should use @ref{map-created-texts}.
This call returns a list of the texts written by a person.
@code{person} is the person whose created texts are to be
......@@ -7565,7 +7566,7 @@ text numbers, each person has a mapping from the N:th text written by
him to the global text number. This function can be used to retrieve
part of that mapping.
@xref{local-to-global} for more information and examples.
More information and examples may be found in @ref{local-to-global}.
@unnumberedsubsec Error codes
......@@ -8512,7 +8513,7 @@ to answer some questions that seem to come up over and over again.
@node What do I have unread
@subsection What do I have unread
Each person has a membership list containing the conferences the persin
Each person has a membership list containing the conferences the person
is a member of. Each element is an object of type Membership. Among
other things it contains the number of the conference, the priority of
the membership, when the person most recently marked a text as read in
......@@ -8718,13 +8719,13 @@ For the mail exporter to work, it will need special privileges.
The main job of the mail importer is to figure out where to deliver mail
and how to deal with threading. The importer can find the recipients in
the @code{To} and @code{CC} headers of the message. The current (very
simple) importer uses addresses like ``p@i{person}@@@i{server}, wherre
simple) importer uses addresses like ``p@i{person}@@@i{server}, where
@i{person} is the number of the recipient and @i{server} is the LysKOM
server.
The importer should add recipients in the @code{CC} header as
carbon-copy-recipients, and recipients in the @code{To} header as
regular recipients. The importer needs to be careful to not deliver
regular recipients. The importer needs to be careful not to deliver
messages to conferences that do not allow messages, even though the
server might not complain.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment