It *sounds* like you're wrting out to a text file then reading it back in again line-by-line. Obviously, if you save out a CR/LF in the middle of some data, this will constitute an end-of-line marker for your 'read' script, splitting your line into two.

Therefore, you probably need to 'escape' \r and \n and then unescape them when you read them back. A common trick, if you are using HTML to display your data, is using something like s/[\r\n]/<br>/g - this will replace all CR/LF with <br> tags. If you want them displayed back as carriage returns, then your 'read' script simply reverses the transformation.

Another common way is to replace with the *string* "\n" (s/\n\/\\n/g;) which again you transform back (s/\\n/\n/g;) when you read it in.

Cheers,
Ben.

In reply to Re: changing data in a file by benn
in thread changing data in a file by simonthom

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.