Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Setting the binary mode in a file open. 1
- Thread starter qwert231
- Start date
You should just need to do:
From the perlfunc man pages:
binmode FILEHANDLE
Arranges for the file to be read or written in "binary"
mode in operating systems that distinguish between
binary and text files. Files that are not in binary mode
have CR LF sequences translated to LF on input and LF
translated to CR LF on output. Binmode has no effect
under Unix; in MS-DOS and similarly archaic systems, it
may be imperative--otherwise your MS-DOS-damaged C
library may mangle your file. The key distinction
between systems that need binmode and those that don't
is their text file formats. Systems like Unix and Plan9
that delimit lines with a single character, and that
encode that character in C as '\n', do not need
`binmode'. The rest need it. If FILEHANDLE is an
expression, the value is taken as the name of the
filehandle.
Cheers, Neil
Code:
open(LAYOUT, $pathS);
binmode( LAYOUT );binmode FILEHANDLE
Arranges for the file to be read or written in "binary"
mode in operating systems that distinguish between
binary and text files. Files that are not in binary mode
have CR LF sequences translated to LF on input and LF
translated to CR LF on output. Binmode has no effect
under Unix; in MS-DOS and similarly archaic systems, it
may be imperative--otherwise your MS-DOS-damaged C
library may mangle your file. The key distinction
between systems that need binmode and those that don't
is their text file formats. Systems like Unix and Plan9
that delimit lines with a single character, and that
encode that character in C as '\n', do not need
`binmode'. The rest need it. If FILEHANDLE is an
expression, the value is taken as the name of the
filehandle.
Cheers, Neil
- Thread starter
- #4
K. That works, but it didn't. What is happening is that when I pull this file in I drop it into an array... to work on it. Then once I modify the various parts of the array, I drop it back into a file. But what is happening is that when I do this, the new file has those box things... wierd characters and spaces... I thought that binmode would fix it, but it doesn't. Any ideas?
- Thread starter
- #5
Hmmm... I see... I still have a problem tho. I still get those funky boxes. Noticed something else. It doesn't do this on all files?! Just the ones I need to parse!
Here is my whole code:
$layout = '810-10-MP-2.txt';
$pathS = '//Dell2400/KPDP2/Layouts/10 Inch MP-2/'.$layout;
open(LAYOUT, "< $pathS"
;
binmode LAYOUT;
@file_data = <LAYOUT>;
print "$#file_data\n";
open JOB, ">>jobfile.txt";
foreach(@file_data) {
print "$_";
print JOB "$_";
if($_ =~ m/FileType:/){
print $_;
}
}
#print JOB @file_data;
close JOB;
close LAYOUT;
Here is my whole code:
$layout = '810-10-MP-2.txt';
$pathS = '//Dell2400/KPDP2/Layouts/10 Inch MP-2/'.$layout;
open(LAYOUT, "< $pathS"
;binmode LAYOUT;
@file_data = <LAYOUT>;
print "$#file_data\n";
open JOB, ">>jobfile.txt";
foreach(@file_data) {
print "$_";
print JOB "$_";
if($_ =~ m/FileType:/){
print $_;
}
}
#print JOB @file_data;
close JOB;
close LAYOUT;
- Thread starter
- #6
Why does my text file come out like this when I pull it into my app:
FileType: Layout
਍䴀㸒“ eNªQ㨀   ¿E䴀㸒“ eNªQ⸀¬Hí¸¬H¿Eഀഀ
਍䐀㸬H㸠eÅÊ’“N e²óªQ㨀   ㄀ഀഀ
਍†eœ`—µ¬HNêÀ›ÅÊ㸪Q®I eÅÊ㨀   ¿E䤀œ`’“èÙÅʪQ¿Eഀഀ
਍…¸ e㸒“ÅÊ㨀   ¿E䘀¿Eഀഀ
਍†eªQÅÊ’“NšÑN e¬H e㸜`ªQêÀN e›ªQ㨀   ¡¡ഀഀ
਍䴀㸗µœ`㨀ഀഀ
Autocrop:
FileType: Layout
਍䴀㸒“ eNªQ㨀   ¿E䴀㸒“ eNªQ⸀¬Hí¸¬H¿Eഀഀ
਍䐀㸬H㸠eÅÊ’“N e²óªQ㨀   ㄀ഀഀ
਍†eœ`—µ¬HNêÀ›ÅÊ㸪Q®I eÅÊ㨀   ¿E䤀œ`’“èÙÅʪQ¿Eഀഀ
਍…¸ e㸒“ÅÊ㨀   ¿E䘀¿Eഀഀ
਍†eªQÅÊ’“NšÑN e¬H e㸜`ªQêÀN e›ªQ㨀   ¡¡ഀഀ
਍䴀㸗µœ`㨀ഀഀ
Autocrop:
-
1
- #7
If the file is binary, then you should really be treating it as if it contains nice newline characters to delimit lines. WHat you should do is slurp the file in to a single scalar, then match just part you need:
Chees, Neil
Code:
open( FILE, $in ) or die;
binmode FILE;
undef $/;
$data = <FILE>;
if( $data =~ /Filetype:(\w+)/ ) { # or similar regexp
print $1;
}- Thread starter
- #9
Here is a portion of the original file:
FileType: Layout
Macros: ~Macros.txt~
Datarecords: 1
Unitofmeasure: ~Inches~
Trace: ~F~
Usecolortransforms: 0
Main:
...
There are no spaces at the end of those lines that Notepad could see. It is a text file. I am doing binmode LAYOUT (that is my filehandle). Slurping it as suggested by Neil does the same thing. The file is created by DP2 Kodak's Digital Production software. (they have developed their own scripting language) But the layouts are supposed to be plain-text. Could it be some form of Unicode?
FileType: Layout
Macros: ~Macros.txt~
Datarecords: 1
Unitofmeasure: ~Inches~
Trace: ~F~
Usecolortransforms: 0
Main:
...
There are no spaces at the end of those lines that Notepad could see. It is a text file. I am doing binmode LAYOUT (that is my filehandle). Slurping it as suggested by Neil does the same thing. The file is created by DP2 Kodak's Digital Production software. (they have developed their own scripting language) But the layouts are supposed to be plain-text. Could it be some form of Unicode?
- Thread starter
- #10
Could it be the way Perl is writing the other file? Acording to Programming Perl (3rd edition) you can specify the binary mode and other I/O Disciplines with commands such as:
open(FH, ">>:raw", $path) or Die "can't open $path: $!";
But I can't get this to work... with 5.6.1. I get an unknown mode error.
open(FH, ">>:raw", $path) or Die "can't open $path: $!";
But I can't get this to work... with 5.6.1. I get an unknown mode error.
- Thread starter
- #11
- Status
Similar threads
