FW: CCCII, EACC, and illegal characters
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Wed, 03 Dec 2003 17:41:48 -0500
- From: Sharon Domier <sdomier@xxxxxxxxxx>
- Subject: FW: CCCII, EACC, and illegal characters
I am not on the list, but my supervisor forwarded this question to me. I
cannot speak for all of the East Asian catalogers out there, but I have
never allowed anyone working for me or with me to input characters directly
into III-CJK because of the CCCII/EACC/Unicode differences.
We have always edited/recataloged in OCLC and then overlaid the older record
in III. If it was a very simple problem, we went in in with normal login,
copied/pasted the EACC code and then logged out and looked at the record
again in CJK mode.
People who thought they could do original cataloging in III and them upload
the records into OCLC found themselves in a whole lot of trouble I expect.
We hear about these problems on the OCLC listserv, when people find OCLC
records that make no sense. When the problem gets tracked back, it is
because the records are being uploaded.
So, I imagine this isn't the answer you want. Good luck with a better
[mailto:innopac-admin@xxxxxxxxxx] On Behalf Of Bob Rasmussen
Sent: Tuesday, December 02, 2003 4:55 PM
To: Innovative Users Group
Subject: CCCII, EACC, and illegal characters
I am working with a library that has been running Innopac for some time,
cataloging books in CJK. They have been working with Innopac set for CCCII
mode. On the client side, sometimes they've been using Anzio, and
sometimes they've been using an add-on such as WinMass. It is Anzio or
Winmass that has accepted a CJK character and sent its "CCCII" code to
Innopac, which simply stores whatever we send it.
The problem: The proper standard for CJK characters is now EACC, which was
a later, more standardized character set than CCCII. They have the same
structure, and Innopac can handle either or both. However, EACC defines
fewer characters than CCCII. The library wants to abide by this standard
(EACC), but they find that their database now contains many illegal
characters - characters that were once "legal" under CCCII.
So the library wants to search and replace these illegal characters with
legal ones. That's where we need help, as follows:
1. Is there an official list of replacement characters for CCCII codes
that are not in EACC?
2. Is there a way to automatically search and replace for a whole list of
In general, how have you dealt with this problem?
....Bob Rasmussen, President, Rasmussen Software, Inc.
personal e-mail: ras@xxxxxxxxxx
company e-mail: rsi@xxxxxxxxxx
voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
fax: (US) 503-624-0760
This message was distributed through the Innovative Users Group INNOPAC list
Public replies: INNOPAC@xxxxxxxxxx
Update your subscription options: