RE: Last Call: draft-klensin-net-utf8 (Unicode Format for Network Interchange) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  *> Upon reciept, the following SHOULD be seen as at least line ending
  *> (or line separating), and in some cases more than that: 
  *> 
  *> LF, CR+LF, VT, CR+VT, FF, CR+FF, CR (not followed by NUL...),
  *> NEL, CR+NEL, LS, PS

I don't know whether you regard this as relevant, but I believe that in
the ARPAnet/early Internet days, FF was not regarded as ending a line.
FF only moved the platen one line at the current character position.  I
believe that this was a formalization of the mechanical operation of a
teletype machine.  This interpretation was also, I believe,
incorporated by Jon Postel in the rules for NVT and for RFC
formatting.

I can't believe I am reopening this old topic... ;-(

Bob Braden


_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]