re: Invalid UTF-8 characters causing MARC::Record crash.

2011-06-17 Thread Edmund Chamberlain
Firstly, hello! Its my first time posting and possibly somewhat predictably with a call for help with Unicode stuff. I've just checked the archive and seen this thread and am having a similar problem, a badly encoded character is causing a while loop through MARC::Batch-next to crash out

Re: Invalid UTF-8 characters causing MARC::Record crash.

2011-06-17 Thread Paul Hoffman
Ed, On Fri, Jun 17, 2011 at 10:53:00AM +0100, Edmund Chamberlain wrote: Firstly, hello! Its my first time posting and possibly somewhat predictably with a call for help with Unicode stuff. Ah, yes... I've just checked the archive and seen this thread and am having a similar problem, a

Invalid UTF-8 characters causing MARC::Record crash.

2011-05-17 Thread Mike Barrett
I'm using MARC::Batch and MARC::Field to iterate through a text file of bibliographic records from Voyager. The unrecoverable error is actually occurring in the Perl Unicode module which is, of course, called by MARC::Record. It's running into invalid UTF-8 character 0xC2. When I looked up the

Re: Invalid UTF-8 characters causing MARC::Record crash.

2011-05-17 Thread Ashley Sanders
Hi, I'm using MARC::Batch and MARC::Field to iterate through a text file of bibliographic records from Voyager. The unrecoverable error is actually occurring in the Perl Unicode module which is, of course, called by MARC::Record. It's running into invalid UTF-8 character 0xC2. When I

Re: Invalid UTF-8 characters causing MARC::Record crash.

2011-05-17 Thread Al
Anybody ever see this before? All. The. Time. When I use Encode.pm version 2.12 I don't have this problem. But it occurs repeatedly with version 2.40. There are a few different solutions, but I'm assuming, like me, that it's not practical for you to clean up your MARC records *before* you

Re: Invalid UTF-8 characters causing MARC::Record crash.

2011-05-17 Thread Dave Sherohman
On Tue, 2011-05-17 at 07:27 -0700, Al wrote: For me I've found the best solution is to leave Encode.pm alone and redefine the offending subroutine within my processing script. I paste this in at the bottom of every script: I always feel a little funny about promoting my own modules, but this