Bug #34844 for Text-RecordParser: cannot parse single or double quotes

Thu Apr 10 17:04:46 2008 useEvil [...] gmail.com - Ticket created

Subject:

cannot parse single or double quotes

I have a field that may contains single or double quotes. Text::RecordParser doesn't seem to like them. I'm not sure why it would die on those characters. 122810 shoxx.com 3 http://www.shoxx.com Oct 26 2005 12:00AM 1, rue de l'Etang, Contern, NA-DE, 5326, GERMANY, info@dretschler.com 23 753 48 16

Sat Aug 30 20:37:47 2008 mike [...] mikebaas.org - Correspondence added

On Thu Apr 10 17:04:46 2008, useEvil wrote: Show quoted text

> I have a field that may contains single or double quotes. > Text::RecordParser doesn't seem to > like them. I'm not sure why it would die on those characters. > > 122810 shoxx.com 3 http://www.shoxx.com Oct 26 2005 12:00AM 1, rue > de l'Etang, Contern, NA-DE, 5326, GERMANY, info@dretschler.com 23 753 > 48 16 >

The module seems to want you to escape single quotes in your source data: my @fields = map { defined $_ && $_ =~ s/\\'/'/g; $_ } ( Not sure if that is the best way to do things.

Sat Aug 30 20:37:55 2008 The RT System itself - Status changed from 'new' to 'open'

Mon Apr 20 21:50:04 2009 kclark [...] cpan.org - Correspondence added 5 min

Since I've already decided to assume that the input has been fixed up by backslash-escaping the input for parse_line, I'm going to go ahead and escape single quotes that look like they haven't already. That should fix your problem, but I am open to suggestions that all of this could be handled better. Should I use a different line parser?

Mon Apr 20 21:50:05 2009 kclark [...] cpan.org - Status changed from 'open' to 'resolved'

Mon Apr 20 21:50:06 2009 kclark [...] cpan.org - Given to KCLARK