Note that if you call warnings() on a MARC::Record object the internal list
of warnings is cleared, so if you call it a second time for the same object
you'll get nothing.
Mike O'Regan
Definitely possible--library automation systems and card printing systems
do it.
I'm not fully conversant with the rules myself, but can tell you that it's
a lot more work than a regex plus a string compare. (I'm thinking of
sorting titles here, actually.) Handling diacritics, sorting "10" a
MARC::Field->as_string() takes a string of subfields rather than an array.
It would be better for as_string() and delete_subfields() to have the same
interface. Since as_string() is used a lot in production,
delete_subfields() should be the one to change.
Mike O'Regan
If your software can be changed to not add 0x1a to the end of a MARC file
then by all means do so. (I don't believe you'll find a specific
prohibition against having it there in the standard, but neither will you
find language anticipating or allowing it. I'm ignoring padding issues for
recor
Yes, \r is legitimate. In MicroLIF you would terminate lines as natural to
the platform. The presumption was that if you transfer files among
platforms they would be treated as text files and line endings translated
as necessary. As always in the bibliographic data world, practices varied,
a
