If you create an example file that contains one good record, and one problematic record, then you'll have a test case that is easier to Dump and share here. Below is a little example that works here and shows an embedded newline being handled correctly by Parse::CSV:

use Parse::CSV;
use Data::Dump 'pp';

my $fh = new IO::File('failing.csv', 'r');

my $fail = do { local $/; <$fh> };
pp $fail;    # Print input
$fh->seek(0,0);

$/ = "\r\n";
my  $parser = Parse::CSV->new(
      handle => $fh,
      csv_attr => { binary => 1 },
);
print pp $_  while $_ = $parser->fetch; # Print output

[download]
Which prints: 
"a,b,c,d,e,f,g\r\na,b,c,\"kkkk\n\",d,e,f,g\r\n"
["a" .. "g"]["a", "b", "c", "kkkk\n", "d" .. "g"]

[download]

In reply to Re^3: issue with LF & CRLF by Loops
in thread issue with LF & CRLF by nafri

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.