Re: Character sets - kind of solved?

On Mon, 6 Dec 2004 08:54:21 -0600 "Doran, Michael D" <[EMAIL PROTECTED]> wrote: > The original record from John Hammer did not contain UTF-8, it contained > MARC-8. I believe that the fact that the combining MARC-8 characters > were replaced by a generic replacement character only indicates that

Updating MARC::File::XML (was Re: Character sets - kind of solved?)

On Mon, 6 Dec 2004 08:54:21 -0600, Doran, Michael D <[EMAIL PROTECTED]> wrote: > > One (perhaps large) caveat: as of now all USMARC records are assumed > > to be MARC-8 encoded, and the data within is always run through > > to_utf8/to_marc8 during XML export/import. > > The MARC-21 standard allows

RE: Character sets - kind of solved?

> One (perhaps large) caveat: as of now all USMARC records are assumed > to be MARC-8 encoded, and the data within is always run through > to_utf8/to_marc8 during XML export/import. The MARC-21 standard allows for either MARC-8 or UCS/Unicode. Position 09 in the record leader indicates the charac

Lintadditions, Errorchecks updates

I have updated my modules and Web site once again. Changes are listed below, including a new module, MARC::Lint::CodeData. MARC::Errorchecks' validate008 subroutine has been revised extensively, reporting errors more consistent with those of the other checking subroutines. MARC::Lint::CodeData: V