I haven't much technical knowledge on this point, but someone gave me a
nice little piece of code which always sets my records straight. So I'll
pass it along
#!/usr/bin/perl -w
$/ = "\x1d\x0a";
while ( my $rec = <> ) {
chomp $rec;
print "$rec\x1d";
}
If it works for you, great! And tha
On Thursday, January 12, 2012 11:59 AM, arvinport...@lycos.com
[mailto:arvinport...@lycos.com] wrote:
>I could have sworn I have processed MARC records containing newlines with no
>problems in the past (I.e., not records converted from XML), though I've never
>tried to validate them with MARCEd
Thanks Terry. I could have sworn I have processed MARC records containing
newlines with no problems in the past (I.e., not records converted from XML),
though I've never tried to validate them with MARCEdit. They were simply
acceptable to III. The MARC-8 character map I use lists both 0A and 0D
I wanted to follow up on this message (saw it through the digest). New lines
actually are invalid characters in a USMARC record. There are a number of
characters that are not allowed, and these happen to be two of them.
Essentially, MARC fields cannot be multi-line. This is why MarcEdit's
M
On Wed, Jan 11, 2012 at 3:35 PM, arvinport...@lycos.com
wrote:
> I've been converting MARC XML records into USMARC and recently had a slew of
> bad records which MARCEdit reported as having invalid leaders. After a few
> days of puzzling over this and blaming it all on Unicode I noticed they wer
