Well, I have a problem with our HTML 'compiler', since we're not only replacing tags, we're converting whole files one line at a time into Javascript (aka the HTML that results from the compiler goes into the converter and ends up inside a document.writeln('');). BUT (and a big but it is), we cannot assume that the HTML we're processing is created on Linux. We have folks on Windows, Linux, and Mac, and we got to deal with all those lines!!!

I'm thinking of doing this:

$file='';
open(IN,"<$filename") || die "$file can't be opened: $!";
{ local $/=undef;  $file=<IN>; }
@lines=split /[\r\n]+/, $file;
foreach $line (@lines) {
   # do some processing here
}

[download]
Any suggestions?

--
$Stalag99{"URL"}="http://stalag99.keenspace.com";

In reply to Handling Mac, Unix, Win/DOS newlines at readtime... by strredwolf

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.