Re: Opening & writing to UTF-8 files; copyright symbol again -- solution

tfile='4788022.edited.bib'; > open (my $output_marc, '>', $outfile) or die "Couldn't open file $!" ; > binmode($output_marc, ':utf8'); > You can set the correct encoding succinctly on opening files e.g. open my $fh, '>:encoding(UTF-8)&

Re: printing UTF-8 encoded MARC records with as_usmarc

uation by > going over it. In the course of preparing the latest edition of the Camel book Tom Christiansen created a Perl Unicode Cookbook see http://www.perl.com/pub/2012/04/perlunicook-standard-preamble.html Its available in a few different places on the web C. -- Colin Campbell Chief Softw

Re: Turning MARC record object back into a string

o some interface that will get upset at MARC's embedded control characters or the character set used in the record. But I suspect thats not a problem because sprintf would not have changed that. Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Li

Re: Finding all the Perl books

gets at irspy.indexdata.com Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 845 557 5634 (phone) +44 (0) 7759 633626 (mobile) colin.campb...@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com

Re: Bug in MARC::Record ?

On 05/01/11 10:21, Paul Poulain wrote: > Hello, > replace >> use Carp qw(croak); > by >> use Carp qw(croak carp); > and things are going much better. > More simply just use Carp; croak and carp (and confess) are exported by default. Colin -- Colin Campbell Ch

Re: Moose based Perl library for MARC records

rrent naming patterns most closely. MooseX is wrong. MooseX is the namespace for extensions to Moose such as new Types. This module should be in the MARC namespace. Something like MARC::NG is called for. Looking forward to using this, Frédéric, good idea Cheers Colin -- Colin Campbell Chief Software En

Re: MARC::Field->subfields function

;s a bit of shaky error handling. subfields checks to see if its a control field, warns that it is then proceeds to try and return the non-existent array. It should just return at that point. I'll take a look at creating a patch for that. Cheers Colin -- Colin Campbell Chief Software

Re: Splitting a large file of MARC records into smaller files

you to break a marcfile into chunks of x-records. man yaz-marcdump for details Cheers Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 208 366 1295 (phone) +44 (0) 7759 633626 (mobile) colin.campb...@ptfs-europe.co

Re: MARC Records, XML, and encoding

Edward Summers wrote: On May 18, 2006, at 6:48 AM, Joshua Ferraro wrote: Anyway, if anyone can shed some light on this I'd be grateful. I believe the data loss you are seeing is due to your source records--not to do with character translation. Just a quick look but I think in many cases the

Re: Corrupt MARC records

cords were "odd" and it took a while to trace it back to this cause. Colin -- Colin Campbell Software Development Consultant Sirsi Ltd

Re: Net::Z3950 and diacritics

values are there. (dumping the record in hex nay reveal something) Cheers Colin -- Colin Campbell Technical Services Consultant Sirsi Ltd [EMAIL PROTECTED]

Re: [patch] Accept # as Blank Indicator

his image: > I'd second that. I've seem software that generated serious problems through confusing the the typographical conventions with the data. Also the fact the space is enclosed in quotes is doing the same thing for the Human reader that LOC's hash is doing (showing it is a space not a null string) Colin -- Colin Campbell Technical Services Consultant Sirsi Ltd [EMAIL PROTECTED]

Re: MARC::Record insert function

nmarc recommends combined alpha and numeric tags for local tags, and I recall seeing them in another Scandinavian format. Colin -- Colin Campbell Technical Services Consultant Sirsi Ltd [EMAIL PROTECTED]

Re: Manuall created records

loppy or Ashley too strict...=) > but for the time being, it seems to work. > The first field terminator should be after the directory (which follows the label) C. -- Colin Campbell Technical Services Consultant Sirsi Ltd [EMAIL PROTECTED]