http://www.perlmonks.org?node_id=1008179


in reply to Re^3: Best Way To Parse Concordance DAT File Using Modern Perl?
in thread Best Way To Parse Concordance DAT File Using Modern Perl?

Thanks, graff!

The problem with having to handle the BOM oneself is that, though it works with Text::CSV_XS-parse(), it doesn't work with Text::CSV_XS->getline().

Suppose we have this multi-line CSV record. There's a literal newline in field five.

my $csv_record = qq{\N{BYTE ORDER MARK}"Field One","Field 2",3,4,"Fiel +d Five" };

How would one parse this record using Text::CSV_XS?

(See the companion thread titled Peculiar Reference To U+00FE In Text::CSV_XS Documentation for more information about this topic.)

Jim

Replies are listed 'Best First'.
Re^5: Best Way To Parse Concordance DAT File Using Modern Perl?
by graff (Chancellor) on Dec 11, 2012 at 07:22 UTC
    Ah. What a pisser. I wonder if you could make Text::CSV_XS work by reading from STDIN... If so, you would just filter out all the BOM characters before feeding the data to your script:
    perl -CS -pe 'tr/\x{feff}//d' < source_file.dat | your_csv_parser ...
    Either that, or else redirect the output of that one-liner to create a cleansed version of the DAT file that has all the BOMs stripped out, and use that "bastardized" version of the data as input to the parser. (I assume that getting the data parsed is more important that preserving its obtuse fixation with BOM characters.)