home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!news.univie.ac.at!apap4.pap.univie.ac.at!schmitt
- From: schmitt@apap4.pap.univie.ac.at (Peter Schmitt, Vienna)
- Newsgroups: comp.text.tex
- Subject: Re: Question: What to do about linefeeds?
- Message-ID: <1992Nov20.141015.57@apap4>
- Date: 20 Nov 92 14:10:15 GMT
- References: <1992Nov19.060810.7717@oucsace.cs.ohiou.edu>
- Distribution: na
- Organization: Vienna University Computer Center
- Lines: 31
-
- In article <1992Nov19.060810.7717@oucsace.cs.ohiou.edu>, carlip@oucsace.cs.ohiou.edu (Walter C3arlip) writes:
- > Ok, here's a dumb question.
- > One of my colleagues is using TeX on two platforms: Macintosh and
- > (yuk) IBM-pc. Evidently, the IBM-pc likes Carriage-Return *and*
- > Linefeed at the end of each line, and when he ports the files to
- > the mac, the linefeeds appear as characters in the file and TeX
- > hates them.
- >
- > I suggested inserting the line:
- > \catcode`^^J=9
- > to tell TeX to just ignore the linefeeds, but this did not seem
- > to help. Anyone know why? Is there an elegant solution to this
- > problem? Is there any reason that IBM-pc's behave in such an anti-social
- > manner?
- >
- (I have not seen an answer yet - therefore:)
- The <eol> symbol(s) is machine dependent - TeX takes this into account and
- reads the files line per line (according to the machine), removes the <eol>
- (and spaces before it) and replaces it by a CR.
- Thus TeX does not see the original <eof>, i.e. the ^^J, and therefore the
- catcode change has no effect.
- There are, however, implementations of TeX which can handle different
- <eol> symbols. I think sbtex (for PC) accepts all the four variants:
- cr, lf, cr/lf, and lf/cr.
- But in general, when transferring a textfile, one has to convert these <eol>
- symbols. There should exist a some tool on a MacIntosh.
- Or use a text editor and use search and replace.
-
- Peter Schmitt a8131dal@awiuni11.edvz.univie.ac.at
- Institute of Mathematics
- University of Vienna schmitt@awirap.bitnet
-