> -----Original Message-----
> From: Ken Hirsch [mailto:[log in to unmask]]
> Tom Emerson wrote:
> 
> >  tr \r \n <file1 >file2
> 
> That will cause everything to be double-spaced, because "\r\n" will be
> changed to "\n\n".

Hmmm... I didn't catch that -- I thought he wanted to change "just" CR's to "just" LF's, but now that I think of it, I think there are three cases:

  - file contains only CR characters -- "tr \r \n" should fix this

  - file contains only LF characters -- this is the desired result [file is OK]

  - file contains CR/LF pairs -- "tr -d \r" should suffice.  (per the man page, the "-d" flag deletes characters found in "string1")

The final flag for tr is "-s", which consolidates repeated occurances of the first character to a single occurance of the output character.  If only one string is passed as a paramter, repeated occurances of the given character are translated to a single occurance of the same character (i.e., "tr -s \n" would remove the extra linefeed, but this would be a second pass)

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *