XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Achieving interoperability in a world where different OS's represent newline differently



On 18 Dec 2014, at 03:26, Rick Jelliffe <rjelliffe@allette.com.au> wrote:

In the first decades of computing, there were two kinds of "newlines".  One was control codes for printers: carriage return and line feed. The other was record start and end signifiers for tape storage: think  COBOL or FORTRAN.

By the 1990s, both kinds of raw newlines had been superseded: drivers hid device details, and Apis took hid drivers.  Newlines were for formatting things on screen or for markup.


Not entirely superseded. UNIX and DOS file systems, and most internet protocols, have great difficulty representing the kind of file that is common on mainframes, where a file is a sequence of records and a record is a sequence of arbitrary bytes, but such files do still exist.

Michael Kay
Saxonica



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS