|
Posted by romerun on August 18, 2006, 8:31 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 Ben Morrow on August 18, 2006, 10:52 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 Uri Guttman on August 19, 2006, 12:07 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 Randal L. Schwartz on August 19, 2006, 6:12 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
|
| Similar Threads | Posted | | Escaping @ in regexps: perl5.6 vs perl5.8 | May 18, 2006, 2:52 pm |
| FAQ 1.4: What are perl4 and perl5? | January 3, 2005, 6:03 pm |
| FAQ 1.4 What are perl4 and perl5? | January 9, 2005, 6:03 am |
| Upgrade Perl5.8.7 | November 28, 2005, 10:54 pm |
| perl5.8.6 won't install on FreeBSD5.3 | March 28, 2005, 9:11 pm |
| FAQ 1.4 What are perl4, perl5, or perl6? | April 26, 2005, 5:03 pm |
| FAQ 1.4 What are perl4, perl5, or perl6? | July 12, 2005, 4:03 am |
| FAQ 1.4 What are perl4, perl5, or perl6? | August 22, 2005, 4:03 pm |
| FAQ 1.4 What are perl4, perl5, or perl6? | December 10, 2005, 5:03 pm |
| FAQ 1.4 What are perl4, perl5, or perl6? | February 7, 2006, 6:03 pm |
|
XML Sitemap