From: alo@kampi.hut.fi (Antti Louko)
Subject: NNTP (oli: Re: RoboCop, lukeeko Robocop newsej{?)
Organization: Helsinki University of Technology
Distribution: sfnet
Date: Thu, 12 Nov 1992 14:56:50 GMT

In article <1drkjkINNio5@cs.tut.fi> po87553@cs.tut.fi (Pasi 'Albert' Ojala) writes:
>In article <KIVINEN.92Nov11183254@laphroaig.cs.hut.fi> kivinen@cs.hut.fi (Tero Kivinen) writes:
>>kukaan halua noudattaa standardeja, eih{n? T{m{nh{n ovat jo useat isot
>>tietokone/ohjelmisto jne. -valmistajat todistaneet.
>>...
>>2.2.  Character Codes
>>
>>   Commands and replies are composed of characters from the ASCII
>>   character set.  When the transport service provides an 8-bit byte
>>   (octet) transmission channel, each 7-bit character is transmitted
>>   right justified in an octet with the high order bit cleared to zero.
>
>Luepa itse tuo uudelleen. Tm ei kerro mitn ISO-merkistst eik
>est sen kytt. Tuo vain sanoo, ett 7-bittist dataa siirrettess
>8bittisell linjalla se ylin bitti nollataan eik jtet miksi sattuu.
>8-bittisten merkkien siirrosta tuo kappale ei puhu halaistua sanaa..!
>
>(niin, tmn joku jo kertoi aikaisemminkin..)

Mutta RFC:t 977, 1036 ja 822 kertovat, ett{ viesteiss{ saa esiinty{
(ainakin siirron aikana vain ASCII-merkkej{. ASCII-merkit ovat
7-bittisi{. On tietenkin sallittua s{il|{ artikkelit paikallisessa
tiedostossa ihan miss{ muodossa tahansa, mutta siirt{{ ei RFCiden
mukaan saa muuta kuin ASCII-merkkej{.

Tekeill{ on menettelytapoja, joilla skandimerkkitukis saadaan
toteutettua j{rkev{ll{kin tavalla, mutta lukekaa hyv{t ihmiset
standardit huolella, jos aiotte nojautua niihin.
----------------------------------------
RFC 977:

3.10.1.  POST

   POST
.
.
.
   If posting is permitted, the article should be presented in the
   format specified by RFC850, and should include all required header
   lines. After the article's header and body have been completely sent
.
.
.
   No attempt shall be made by the server to filter characters, fold or
   limit lines, or otherwise process incoming text.  It is our intent
   that the server just pass the incoming message to be posted to the
   server installation's news posting software, which is separate from
   this specification.  See RFC850 for more details.
----------------------------------------
RFC 1036:

Network Working Group                                          M. Horton
Request for Comments:  1036                       AT&T Bell Laboratories
Obsoletes: RFC-850                                              R. Adams
.
.
    within the Internet standard.  Therefore, the rule is adopted that
    all USENET news messages must be formatted as valid Internet mail
    messages, according to the Internet standard RFC-822.  The USENET
    News standard is more restrictive than the Internet standard,
    placing additional requirements on each message and forbidding use
    of certain Internet features.  However, it should always be possible
    to use a tool expecting an Internet message to process a news
    message.  In any situation where this standard conflicts with the
    Internet standard, RFC-822 should be considered correct and this
    standard in error.
----------------------------------------
RFC 822:
.
.
     3.  LEXICAL ANALYSIS OF MESSAGES

     3.1.  GENERAL DESCRIPTION

          A message consists of header fields and, optionally, a body.
     The  body  is simply a sequence of lines containing ASCII charac-
     ters.  It is separated from the headers by a null line  (i.e.,  a
     line with nothing preceding the CRLF).
.
.
. ja relevantit osat syntaksis{{nn|ist{:
     CHAR        =  <any ASCII character>        ; (  0-177,  0.-127.)
     message     =  fields *( CRLF *text )       ; Everything after
                                                 ;  first null line
                                                 ;  is message body
     text        =  <any CHAR, including bare    ; => atoms, specials,
                     CR & bare LF, but NOT       ;  comments and
                     including CRLF>             ;  quoted-strings are
                                                 ;  NOT recognized.
Xref: sparky sfnet.atk.sodat:642 sfnet.tietoliikenne.viestinviejat:12