> I have to admit my Perl skill is very limited, so this may be a dumb
question,
> but I can't seem to find answer. When I use MARC::Batch to read
records from
> our catalog (III) export file, I can't seem to find a way to skip an
error
> record. When I ran the following against an III export M
I recently came across a nasty issue with MARC::Record to do with output of
Marc-8 encoded records. I was converting XML (which was in UTF-8) into MARC
records using MARC::Record and had initially, and successfully, got good UTF-8
encoded MARC records out at the end.
However, I then could not
> -Original Message-
> From: Shelley Doljack [mailto:sdolj...@stanford.edu]
> Sent: 31 July 2012 20:18
>
> The problem was I wasn't telling perl to output UTF-8. Now that I added
> binmode(FILE, ':utf8') to my script, the problem is fixed. However, it sounds
> like once I set binmode to UTF
> You also could consider to grok Jason Thomale's "Interpreting MARC:
> Where's the Bibliographic Data?" < http://journal.code4lib.org/articles/3832 >
That's a very good article, as it highlights the problems of the prescribed
punctuation both getting in the way of extracting parts of the data an
Not sure exactly what you mean by not using a mailer.
In our Perl scripts I tend to do:
open (MAIL, "|-", '/bin/mailx', '-s', $subject, @addresses)
|| die "Failed to e-mail report: $!\n";
print MAIL $report;
close MAIL;
which relies on mailx being installed and able to send messages.
I’
> On Wed, Nov 19, 2014 at 02:19:26PM +0000, PHILLIPS M.E. wrote:
> > open (MAIL, "|-", '/bin/mailx', '-s', $subject, @addresses)
> > || die "Failed to e-mail report: $!\n";
>
> what's the point of using perl then?
Ther
The copyright symbol is not one of the characters for which there are two
representations.
One thing that can confuse people about Unicode is the distinction between the
“code point”[1] and the representation of the code point in the various Unicode
transformation formats such as UTF-8, UTF-16,
> You can set the correct encoding succinctly on opening files
> e.g. open my $fh, '>:encoding(UTF-8)', $outfile
You might also see this even more succinct variant:
open my $fh, '>:utf8', $outfile
though technically speaking, that will not give you guaranteed conformant UTF-8
because it could
> However, combining Jon Gorman's recommendation with some Googling, I get:
>
> my $outfile='4788022.edited.bib';
> open (my $output_marc, '>', $outfile) or die "Couldn't open file $!" ;
> binmode($output_marc, ':utf8');
>
> The open statement may not be quite correct, as I am not familiar with t
