Path: cdrom.com!barrnet.net!decwrl!hookup!europa.eng.gtefsd.com!howland.reston.ans.net!EU.net!news.funet.fi!ngw!news.funet.fi!not-for-mail
From: Jon Hall <J.M.Hall@SOTON.AC.UK>
Newsgroups: alt.cd-rom
Subject: Re: text files in ISO9660
Date: 28 Feb 1994 21:34:27 +0200
Organization: FUNET-NGW
Lines: 35
Sender: daemon@news.funet.fi
Distribution: alt
Message-ID: <199402281906.TAA17626@mail.soton.ac.uk>
Reply-To: Jon Hall <J.M.Hall@SOTON.AC.UK>
NNTP-Posting-Host: news.funet.fi
Return-Path: <@UCCVMA.UCOP.EDU,@RELAY.SOTON.AC.UK:J.M.Hall@SOTON.AC.UK>
Via: uk.ac.soton.relay; Mon, 28 Feb 1994 19:12:50 +0000
X-Mailer: ELM [version 2.3 PL11]
To: CDROM-L Redistribution <lst-alt-cd-rom@NGW.FUNET.FI>
In-Reply-To:  <199402260853.IAA00138@mail.soton.ac.uk>; from "Elisha Polomski"
              at Feb 25, 94 7:10 pm

> Recently a customer told me that text files written
> under UNIX and formatted in iso9660 were difficult to read
> on a Mac. Apparently a MAC uses CR> for a new line,
> and UNIX uses line feed. Is this true?

Yes.

> Has anyone encountered this problem?

Almost certainly :-)

> What is the standard way test files should be written for
> MAC, PC, and UNIX machines?

I don't think there is one (I assume you mean "text" instead of "test"
above). Using PC formatted text files (see below) will probably maximize
the chance of reading the file on screen, but the unwanted characters
will almost certainly cause problems within certain applications.

> What kind of characters does each mavchine expect at the end of line?

Mac -           CR only (0D hex)
Unix -          LF only (0A hex)
PC (DOS) -      CR followed by LF (0D 0A hex)

> thanks,
> Elisha

Hope this helps.

--
Jon Hall                                  | Tel:      +44 (0)703 592274
Senior Programmer                         | Fax:      +44 (0)703 593033
Institute of Sound and Vibration Research | JANET:    J.M.Hall@uk.ac.soton
University of Southampton, UK             | Internet: J.M.Hall@soton.ac.uk
