|
Posted by yezi on August 3, 2005, 3:54 pm
Please log in for more thread options
>>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,
> There
> is a rogue carriage return (0xd) in the string
> Is there something I can do to deal with this
> situation?
Repair the corrupted file:
perl -p -i -e 'tr/\r//d' bad_file
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
|
|
Posted by Ian Wilson on August 4, 2005, 9:21 am
Please log in for more thread options
>>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,
> There
> is a rogue carriage return (0xd) in the string
> Is there something I can do to deal with this
> situation?
Repair the corrupted file:
perl -p -i -e 'tr/\r//d' bad_file
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
|
|
Posted by chris-usenet on August 4, 2005, 11:47 am
Please log in for more thread options >>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,
> There
> is a rogue carriage return (0xd) in the string
> Is there something I can do to deal with this
> situation?
Repair the corrupted file:
perl -p -i -e 'tr/\r//d' bad_file
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
|
|
Posted by ????? ????? (Shantanoo Mahajan on August 12, 2005, 1:51 am
Please log in for more thread options >>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,
> There
> is a rogue carriage return (0xd) in the string
> Is there something I can do to deal with this
> situation?
Repair the corrupted file:
perl -p -i -e 'tr/\r//d' bad_file
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
|
| Similar Threads | Posted | | Looking for a module/program author, or help with program... | September 7, 2005, 6:00 pm |
| FAQ 1.11: When shouldn't I program in Perl? | October 26, 2004, 5:03 pm |
| FAQ 1.11: When shouldn't I program in Perl? | November 10, 2004, 6:03 pm |
| First Perl Program | November 16, 2004, 2:04 pm |
| FAQ 1.11: When shouldn't I program in Perl? | December 20, 2004, 6:03 pm |
| FAQ 1.11 When shouldn't I program in Perl? | January 10, 2005, 6:03 pm |
| FAQ 1.11 When shouldn't I program in Perl? | April 6, 2005, 11:03 pm |
| FAQ 1.11 When shouldn't I program in Perl? | June 22, 2005, 5:03 am |
| FAQ 1.11 When shouldn't I program in Perl? | August 21, 2005, 10:03 am |
| FAQ 1.11 When shouldn't I program in Perl? | December 3, 2005, 5:03 pm |
|
XML Sitemap