Re^2: line ending problem Text::CSV alternative Text::ParseWords?

[GertMT]

in reply to Re: line ending problem Text::CSV alternative Text::ParseWords?
in thread line ending problem Text::CSV alternative Text::ParseWords?

that gives me:

# CSV_XS ERROR: 2023 - EIQ - QUO character not allowed

and nothing further.

If I leave out the auto_diag = 1 part I get nothing back on the screen.

[Tux]

From the man page:

       2023 "EIQ - QUO character not allowed"
         Sequences like ""foo "bar" baz",quux" and "2023,",2008-04-05,
+"Foo,
         Bar",\n" will cause this error.

Can I see the actual data?

update: FWIW those errors might go away if you parse with

Text::CSV_XS->new ({ binary => 1, allow_loose_quotes => 1 });

or

Text::CSV_XS->new ({ binary => 1, escape_char => undef });

[GertMT]

that is magic for me. Where did you get this man page from.

Great that you want to have a look at it. The file is created by a Filemaker DB (fmpro 6 --> Export CSV: output file character set: Macintosh). Would it be possible to e-mail you this? It is not that big, less then 500kb

If I would just cut and paste it'll probably all work just fine as with opening and saving the script works fine.

[Tux]

That info is standard info in man Text::CSV_XS or perldoc Text::CSV_XS. Also available in the on-line DIAGNOSTICS

You can e-mail it to h dot m dot brand at xs4all dot nl or make it available by url. Size is not a problem.