To help prevent installation problems with Windows Vista, 7, 8/8.1 and 10, please right-click the file you downloaded and click Run as Administrator

Getting ready for Unicode

This release of Connexion client 2.63 is part of a group of changes that OCLC is making to expand WorldCat support for full Unicode characters and scripts to better represent your international collections. When complete, WorldCat will expand support from 15 scripts to all scripts that are represented in Unicode.

This means that by the end of 2016, WorldCat users will have the ability to:

Catalog using full Unicode (available now in Connexion client 2.63)

Upload records with full Unicode

Search across full Unicode

As you catalog using Connexion client 2.63 please be aware that:

WorldCat now supports all Unicode characters. OCLC has removed all limitations on MARC-8 and selected non-MARC-8 scripts. If you rely on validation to block unsupported characters, you may need to update impacted workflows.

Connexion client 2.63 supports all Unicode characters through version 8.0.0 of Unicode.

You can use previously unsupported characters to add new bibliographic records to WorldCat, replace records in WorldCat, import records into the client and export records from the client. All other functions for bibliographic records support these characters as well.

You will not be able to use the newly supported characters to search WorldCat until later in 2016. OCLC will announce when searching for the new characters in WorldCat is ready to use.

Authority records continue to be limited to the MARC-8 character set.

You have a choice to export bibliographic records in MARC-8 (the default) or in UTF-8. If non-MARC-8 scripts are exported in MARC-8 data format, the non-MARC-8 characters are saved in Numeric Character Reference (NCR) format.

Valid Unicode characters can appear as empty boxes if they are not supported in your default font.

The Arial Unicode MS font that OCLC recommends will not support all scripts. You will have to search for fonts to cover some of the new scripts OCLC supports. Fonts that support these scripts vary in their ability to display characters outside of the script they were designed to support. You may have to experiment to see which font works best for your needs for a particular script. The font selected as the default in the client is applied to the entire record. You may have to move between two fonts to see all of the characters in a record.