Re^2: TEXT::CSV Error 2032

Completely wrong. All of it. Text::CSV_XS automatically deals with CR and/or NL in CSV streams/files.

When in doubt, read the manpage:

2023 "EIQ - QUO character not allowed" 

Sequences like "foo "bar" baz",quux and 2023,",2008-04-05,"Foo, Bar",\
+n will cause this error.
[download]

update: Sorry for that tone. I got sidetracked by the wrong paste in the OT. He used a message-code mismatch. I look at codes

2032 "EIF - CR char inside unquoted, not part of EOL"
[download]

2032 != 2023. Most of the time, NOT passing eol to the constructor is likely to solve the issue

Enjoy, Have FUN! H.Merijn

Comment on Re^2: TEXT::CSV Error 2032 Select or Download Code

Replies are listed 'Best First'.
Re^3: TEXT::CSV Error 2032 by Happy-the-monk (Canon) on Jun 25, 2012 at 16:58 UTC
Text::CSV_XS automatically deals with CR and/or NL in CSV streams/files. Well the documentation (that I claim not to know :-P) says otherwise: This means that fields can not contain newlines. If your data contains newlines embedded in fields, or characters above 0x7e (tilde), or binary data, you must set binary => 1 in the call to new (). To cover the widest range of parsing options, you will always want to set binary. Still I haven't been able to reproduce the OP's error yet. Cheers, Sören	[reply]
Re^4: TEXT::CSV Error 2032 by Tux (Canon) on Jun 25, 2012 at 17:04 UTC
The OP did add `binary => 1` in the constructor, so that part of the doc is not applicable to this problem IMHO. Again sorry for the harsh tone in my first reply. Appreciate your help to people with questions. Enjoy, Have FUN! H.Merijn	[reply] [d/l]
Re^4: TEXT::CSV Error 2032 by endymion (Acolyte) on Jun 26, 2012 at 06:26 UTC
False alarm . I have found the problem. Now it works. There were hidden ^M chars in the file. For other user, got this problem. With substitute s/^M//g I solved the error. Thanks Tux for the right direction.	[reply]
Re^4: TEXT::CSV Error 2032 by endymion (Acolyte) on Jun 26, 2012 at 06:14 UTC
Hello Monks, the chomp was not the problem :-(. I also tried to substitute the newlines. Very strange.	[reply]