 |
 |
That sequence is definitely not legal. In order to imbed ASCII with an EACC sequence, the appropriate escape sequences must be used. A valid version of this string would be
1b 24 31 21 50 56 4b 37 6f 69 24 4e 21 51 31 21 47 34 69 24 4e 21 30 70 21 51 2b 1b 28 42 7b 36 39 32 34 66 36 7d
possibly followed by 1b 24 31 if more EACC coding follows. I don't know whether this deviation is frequent or not. OCLC software would also report 7b 36 39 as invalid EACC and refuse to process the record.
Gary L. Smith
Software Architect
OCLC
From: MARC [mailto:[log in to unmask]] On Behalf Of Godmar Back
Sent: Thursday, March 22, 2012 09:00
To: [log in to unmask]
S
ubject: {ASCII} within EACC string
Hi,
Ed Summers suggested I pose the following question to this email list.
In a MARC record exported by a vendor system (III) a 880$a subfield, which contains a Japanese title in EACC, contains these bytes:
1b 24 31 21 50 56 4b 37 6f 69 24 4e 21 51 31 21 47 34 69 24 4e 21 30 70 21 51 2b 7b 36 39 32 34 66 36 7d 1b 28 42
(colors used for easier reading), which III interprets as
米国の統治の仕組{6924f6}
In other words, they embed ASCII {6024f6} inside of an EACC string that consists of 24-bit EACC characters, but then embeds ASCII within { } before the next ESC sequence.
When processing this record with pymarc (a Python library for MARC processing), problems oc
cur because 7b 36 39 is not a valid EACC character encoding.
My question: is the above byte sequence legal, and if not, does it, or similar sequences, constitute a frequent deviation (so it would be worthwhile to recognize and work around it in pymarc?)
- Godmar