The cause of the "odd" output is the carriage return character you're leaving on the end of $new_string. I assume you're running this code on UNIX so that $/ is set to "\n" and chomp() removes only the newline, leaving the carriage return, which when output to the display device repositions the point at the beginning of the line.

You could get rid of the carriage return by assigning the proper record separator string to a dynamic copy of $/: 

{
    # localized global variable
    # this copy of $/ is visible only within this block
    # and to subroutines called from within the block.
    local $/ = "\r\n";
    while (<I>) {
        next unless /Physical Address/;
        /:/;    # why is this here?
        chomp;  # chomp now removes "\r" in addition to "\n"
        ...
}

[download]

In reply to Re: I need help with pattern matching by converter
in thread I need help with pattern matching by kirk123

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.