Let me try to simplify that a bit ...
use Text::CSV_XS;
my $csv = Text::CSV_XS->new ({
auto_diag => 1, # Let Text::CSV_XS do the analysis
always_quote => 1,
binary => 1,
eol => $INPUT_RECORD_SEPARATOR,
});
binmode STDOUT, ':encoding(UTF-8)';
for my $file (@ARGV) {
open my $fh, '<:encoding(UTF-8)', $file;
while (my $fields = $csv->getline ($fh)) {
$csv->print (*STDOUT, $fields); # no need for a reference
}
# due to auto_diag, no need for error checking here
close $fh;
}
If this script is to sanitize CSV data, I'd advice TWO csv objects. One for parsing, that does not pass the always_quote and eol attribute, and one for output. The advantage is that all legal line-endings are parsed well automatically, even if mixed.
I have no neat way to the BOM problem other than what you already use.
Enjoy, Have FUN! H.Merijn
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.