I shared this thread with the support people at Bare Bones Software.
This was their reply:
Hi Rick,
TextWrangler always uses \r (ASCII 13, the canonical carriage return)
internally, but you can tell it to use any desired representation on
disk for the line endings: Mac (CR), Unix (LF), or
On Feb 10, 2006, at 18:17, Rick Triplett wrote:
I've encountered a perplexing file-reading difficulty.
I pasted some dictionary definitions from a web page into Word and
saved them as a text file. All the odd numbered lines had terms and
their following even numbered lines had definitions.
On 2/10/06, Rick Triplett <[EMAIL PROTECTED]> wrote:
snip
> My perplexities are these: Why did TextWrangler show \r for the line
> endings after I had save them for Unix (\n)? And, why did Perl have
> difficulty with the line endings in the first place? Perl is supposed
> to be sensitive to the ope
I've encountered a perplexing file-reading difficulty.
I pasted some dictionary definitions from a web page into Word and
saved them as a text file. All the odd numbered lines had terms and
their following even numbered lines had definitions. My goal was to
convert every other line ending
