Thanks for the responses! I was also contacted off-list by
Net::OAI::Harvester's maintainer and we tracked the issue down to a rogue
standalone release of XML::SAX::Base. Removing that, so that the
XML::SAX::Base included with XML::SAX was used instead, resolved my problems
and I was then abl
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 th