how to add carriage returns

cat -vte file.name

See "man cat".

The -v says show control characters preceeded with a ^

The -t says show tabs as ^T

The -e says show end-of-line as $

Check out the thread at

http://hints.macworld.com/article.php?story=20031018164326986

Or: from http://sed.sourceforge.net/sed1line.txt :
Using the Unix stream editor sed (type man sed in Terminal for usage):

# IN UNIX ENVIRONMENT: convert DOS newlines (CR/LF) to Unix format.
sed 's/.$//' # assumes that all lines end with CR/LF
sed 's/^M$//' # in bash/tcsh, press Ctrl-V then Ctrl-M
sed 's/\x0D$//' # works on ssed, gsed 3.02.80 or higher

# IN UNIX ENVIRONMENT: convert Unix newlines (LF) to DOS format.
sed "s/$/`echo -e \\\r`/" # command line under ksh
sed 's/$'"/`echo \\\r`/" # command line under bash
sed "s/$/`echo \\\r`/" # command line under zsh
sed 's/$/\r/' # gsed 3.02.80 or higher

# IN DOS ENVIRONMENT: convert Unix newlines (LF) to DOS format.
sed "s/$//" # method 1
sed -n p # method 2

# IN DOS ENVIRONMENT: convert DOS newlines (CR/LF) to Unix format.
# Can only be done with UnxUtils sed, version 4.0.7 or higher. The
# UnxUtils version can be identified by the custom "--text" switch
# which appears when you use the "--help" switch. Otherwise, changing
# DOS newlines to Unix newlines cannot be done with sed in a DOS
# environment. Use "tr" instead.
sed "s/\r//" infile >outfile # UnxUtils sed v4.0.7 or higher
tr -d \r <infile >outfile # GNU tr version 1.22 or higher

I think you need to replace the UNIX CR terminator with a WINDOWS CRLF terminator.
Try:

sed 's/$/'$' ''/' unixfile.txt > windowsfile.txt

or

awk 'sub("$", " ")' unixfile.txt > windowsfile.txt

I've you're unsure of the line endings, the following will take care of pc and legacy mac lines (it will also leave unix lines unchanged):
<pre style="border: 1px solid #ddd; padding-left: .75ex; padding-top: .25em; padding-bottom: .25em; margin-top: .5em; margin-bottom: .5em; margin-left: 1ex; max-width: 40ex; overflow: auto; font-size: 10px; font-family: Monaco, 'Courier New', Courier, monospace; color: #444; background: #eee; line-height: normal">perl -pi -e 's/\r\n?/\n/g'</pre>

When I used to work in DOS, we had a way of displaying the file where the actual hex codes were on the left and the ascii equivalents were on the right.
Is such a thing or similar available from terminal or shareware stand alone app.

Try hexdump:
<pre style="border: 1px solid #ddd; padding-left: .75ex; padding-top: .25em; padding-bottom: .25em; margin-top: .5em; margin-bottom: .5em; margin-left: 1ex; max-width: 40ex; overflow: auto; font-size: 10px; font-family: Monaco, 'Courier New', Courier, monospace; color: #444; background: #eee; line-height: normal">hexdump -C your-file</pre>

Did you try Bob's suggestion?
What to you get with: cat -vte file.name
(print a few lines here. enclose with: \{code\} ... \{code\} without the '\' )

Very strange. What does the 'file' command report? (i.e. file filename.txt).

?M-^@?

M-^ looks like 94 dec. Add 128 (high-bit) = 222, convert to hex = de.
sed can strip this with:
{code}
s/'$'\xde''$//
{code}

...but I'm not sure of the other characters, or why cat is reporting a '?'


If you post the url where you got the lyrics, I'll take a look.

I just thought of something. Give textutil a try:

textutil -convert txt yourfile.txt -output foo.txt

Please ask some Microsoft folks about your Microsoft Office software.

Given cut-and-paste works most everywhere else, there's likely a setting or tool or wizard here that can adjust the particular cut-and-paste behavior here.

My guess is that the approach here of reverse-engineering sequential file formats isn't the way that the Microsoft folks expected this to work.

Post code or anything you want to forum to ignore is done using

...
... your stuff as is here ...
...

Everything between the matching {code} pair will be presented as it, with all indentation and without the forum stealing characters thinking they are forum meta-formatting instructions.

Another utility you might look at is iconv. For example the log format for Retrospect was recently switched to an MS unicode flavor. I discovered I could convert it to utf8 with the following command:
<pre style="border: 1px solid #ccc; padding-left: .75ex; padding-top: .25em; padding-bottom: .25em; margin-top: .5em; margin-bottom: .5em; margin-left: 1ex; max-width: 60ex; overflow: auto; font-size: 10px; font-family: Monaco, 'Courier New', Courier, monospace; color: #444; background: #eee; line-height: normal">iconv -f UCS-2LE -t UTF-8 operations_log.utx</pre>