Phoenix Network Forums

I use perl and when I try to get file via http (I use IO::Socket::INET) it is damaged. Every \x0A byte is replaced in it on \x0D\x0A. How to fix it .

P.S. I can not use other modules !!!

can we see the script?

var a is the input you get from the script.

a ~= s/\x0D\x0A/\x0A/g;

Or something ike that--I'm more of a C coder myself.

The file isn't damaged. In fact, everything is alright. It just shows that the file has certainly been written on a Windows system. But as long as you don't know why the file is 'damaged', and how you could 'fix' it, you shouldn't be writing network applications (no matter how small they are).

generally you should transfer in binary mode, if not using human readable files . in that case the file syste will not try to convert to your local encoding .

if you don't mind running another program exec dos2unix. This is exactly what it does.

Or in perl itself:
(took 30 seconds to find in google)

http://www.technocage.com/~caskey/dos2unix/


#!/usr/bin/perl -w
#
# A script to convert a number of java source
# files from dos line ending format to unix line format.
#
# WARNING: THIS SCRIPT DOES NOT CHECK FOR PRE-EXISTING
# FILES, USE WITH CAUTION.
#
# Usage: dos2unix <DIRECTORY>
#

$directory = shift @ARGV;
$directory = '.' unless $directory;
chdir( $directory ) || die "Unable to enter directory '$directory'.\n$!\n";

@files = <*.java>;
$| = 1;
$linesFixed = 0;
foreach( @files ) {
print "$_\t";
open(INPUT, "<$_");
rename( $_, "$_.bak") || die "Unable to rename $_\n$!\n";
open(OUTPUT, ">$_");
while(<INPUT>) {
if ( s/\r\n/\n/ ) {
$linesFixed++;
}
print OUTPUT;
}
} continue {
print "($linesFixed)\n";
$linesFixed = 0;
close INPUT;
close OUTPUT;
}

De Kus wrote:generally you should transfer in binary mode, if not using human readable files :D. in that case the file syste will not try to convert to your local encoding :).

He is using HTTP, which doesn't care about line-feed encoding or binary vs. text mode. It just delivers what it gets. The best thing is to interpret the CR character properly, because it's not totally meaningless. Remember, a CR doesn't necessarily have to be followed by an LF.