Don't forgot to use binmode. Some operating systems will play tricks with the line endings when you write to a file unless they're told explicitly not to.

Here's the converter I use. It converts to either CR, CRLF, or LF depending on what you specify to -n, and can modify a single file, multiple files, or all the files in a directory using File::Find:

#!/usr/bin/perl -w
use strict;
use Getopt::Std;
use File::Find;



# get the options:
my %opts;
getopts('f:n:h', \%opts) || usage();
usage() if (!$opts{'n'} || $opts{'h'});

# if no files were specified, we'll convert everything in the current 
+directory:
push(@ARGV, '.') unless @ARGV;

my $newline = $opts{'n'};
usage() if ($newline =~ /[^CRLF]/i);

$newline =~ s/CR/\015/i;
$newline =~ s/C/\015/i;
$newline =~ s/R/\015/i;
$newline =~ s/LF/\012/i;
$newline =~ s/L/\012/i;
$newline =~ s/F/\012/i;

foreach my $filename (@ARGV)
{
    # traverse the directory tree and look at each file:
    find(sub { convertNewlines() }, $filename);
}





sub convertNewlines
{
    my $filename = $_;
    
    # don't mess with it unless it's a text file:
    return unless (-T $filename);

    open(FILE, "< $filename")
        or die "Couldn't open file ($filename) for reading: $!";

    my $converted_text;
    my $line_endings_converted = 0;
    while (my $line = <FILE>)
    {
        $line_endings_converted +=
            ($line =~ s/(?:\015\012|\015|\012)/$newline/g);
        $converted_text .= $line;
    }

    # now save it, and binmode it so no additional conversion is done 
+to
    # the line endings:
    open(FILE, "> $filename")
        or die "Couldn't open file ($filename) for writing: $!";
    binmode FILE;
    print FILE $converted_text;
    close FILE;

    print "Converted $line_endings_converted newlines in \"$filename\"
+ " .
          "to $opts{'n'}.\n";
}





sub usage
{
    print <<'END_OF_USAGE';
This script can be used to convert the line endings in files to Unix, 
+Windows,
or MacOS line endings.

Usage:
 $ newlines -n NEWLINE [FILENAMES...]

Arguments:
    -n   The newline sequence that the line endings in the files you
         specified should be converted to. Either "CR" or "R" for carr
+iage
         return, "LF" or "L" for linefeed, or "CRLF" for carriage
         return/linefeed.
Flags:
    -h   Displays this message.
END_OF_USAGE

    exit;
}
[download]

For example, this:

newlines -n CRLF foo.txt bar.txt foo_bar.txt stuff.* ./more_text_files

converts the line endings in "foo.txt", "bar.txt", "foo_bar.txt", the text files in the current directory named "stuff" with any extension, and all of the text files in "./more_text_files" to CRLF (\015\012).

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.