On Tue, Jan 21, 2014 at 12:38 PM, Galen Charlton wrote:
> Hi,
>
> I have uploaded [1] version 1.0.2 of MARC::File::XML. This is a
> security release that repairs an XML external entity (XXE)
> vulnerability. I recommend that all uses of MARC::File::XML upgrade
> promptly.
>
> Here is the change
On Sat, Feb 9, 2013 at 11:06 PM, Galen Charlton wrote:
> Hi,
>
> I have uploaded version 2.0.4 of MARC::Record to CPAN. This is a minor
> functionality and bugfix release.
Thanks Galen - I'm in the process of getting the Fedora packages pushed to
rawhide, Fedora 18, and Fedora 17 now.
Dan
As the subject says:
https://bugzilla.redhat.com/show_bug.cgi?id=830221 is the bug I opened
in hopes of getting Library::CallNumber::LC packaged for Fedora.
Fingers crossed.
--
Dan Scott
Laurentian University
these packages.
I'll let you know when / if I have good news :)
--
Dan Scott
Laurentian University
these packages.
I'll let you know when / if I have good news :)
--
Dan Scott
Laurentian University
ence in the versions of perl on your two systems?
For what it's worth, "Mixing reads and writes" in perlopentut says
that you probably want:
open (my $DATEFILE, "+<", $date_file) ...
(and making that change to my copy of your script makes it work for me).
--
Dan Scott
Laurentian University
me concern. Keeping everything under
MARC:: may also make it a tiny bit easier to find the existing
alternatives for, well, parsing MARC records. I would +1 MARC::Moose.
Also, to be purely pedantic, "MARC" is an acronym for
"MAchine-Readable Cataloguing", while "Marc" is a
the near term are likely to be in the
area of cleaning up copyright statements (2004, eh?) and general
documentation, so the VCS doesn't matter much to my (potential)
workflow.
--
Dan Scott
Laurentian University
Was it decided that Bill's escaping output patch would be dropped? I
don't see it in CVS yet.
It would be nice to see the 0.91 release get pushed out the door, in
any case. 0.88 was a long time ago.
Dan
2009/4/14 Galen Charlton :
> Hi,
>
> On Tue, Apr 14, 2009 at 3:57 P
ruction. I'm not sure if it's the best
> approach, but it got me up and running again.
>
> Thanks,
Is anyone planning on applying this patch? It would be a shame to drop
it on the floor.
--
Dan Scott
Laurentian University
for File_MARC (PHP)... and a nice horrible MARC record
from the wild would help.
--
Dan Scott
Laurentian University
family
> of modules does have at least some Unicode support.
>
> The place to ask is the perl_for_librarians mailing list, so I have copied my
> reply to them.
In a nutshell, MARC8 to UTF8 (Unicode) conversions are supported by
MARC::Charset (http://search.cpan.org/dist/MARC-Charset/)
--
Dan Scott
Laurentian University
ot;.$r->subfield(100 => 'a');
And while you're at it, s/charater/character/ please :)
--
Dan Scott
Laurentian University
With MARC::Charset 0.96, MARC::Record 2.0.0, and MARC::File::XML from
CVS, I get failed tests for 7 out of 8 of Joshua's tests. Test STDIN
and STDOUT output attached.
Dan Scott
On 16/04/07, Joshua M. Ferraro <[EMAIL PROTECTED]> wrote:
- "Mike Rylander" <[EMAIL PRO
14 matches
Mail list logo