Skip Menu |

This queue is for tickets about the Text-RecordParser CPAN distribution.

Report information
The Basics
Id: 42436
Status: resolved
Worked: 1 hour (61 min)
Priority: 0/
Queue: Text-RecordParser

People
Owner: kclark [...] cpan.org
Requestors: technik [...] auxion.de
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: v1.2.1
Fixed in: (no value)

Attachments


Subject: error in parsing files
Hi there; I have the following problem with Text::RecordParser When I open one of this files (attached) with $p->filename(LOC_ON_DISK) I only get loaded (2nd File with 114 lines from >1900) And 1st file with 481 lines ( from 3000 ) Is there any limitation or anything what can explain this behavior? Is there any function what returns me some feedback Perl Version: , v5.8.8 Server : Linux s-esl7 2.6.21.2
Subject: b2ba02a993f686cf162b2b0caff98ce6.gz

Message body not shown because it is not plain text.

Subject: b2ba02a993f686cf162b2b0caff98ce6-2.gz

Message body not shown because it is not plain text.

On Jue. Ene. 15 06:22:30 2009, technik@auxion.de wrote: Show quoted text
> Hi there; > > I have the following problem with Text::RecordParser > > When I open one of this files (attached) with > $p->filename(LOC_ON_DISK) > > I only get loaded (2nd File with 114 lines from >1900) > And 1st file with 481 lines ( from 3000 ) > > Is there any limitation or anything what can explain this behavior? > Is there any function what returns me some feedback > > Perl Version: , v5.8.8 > Server : Linux s-esl7 2.6.21.2
I could locate the error in the FILE Text::ParseWords.pm the error was/is that in the file, who has dataset seperator ;- Simikolon Sign, inside the data there aree a couple of "-QUOTE Signs (3,5" Disk) and when the ParseWords reaches it, he gives up at line 58 becaus he does not recognizes the "-Sign as "normal" Sign inside the text To get away from this i pass the file thru a =~ s to change it to HTML Sign (is what is neadet at the moment) but for the futur would be great that this works (like passing Bad-HTML Code) Thanks!
Looks like the user figured out the problem and a solution.