 |
 |
How can there be a character that you can't at least serialize as a hex code? Ralph > -----Original Message----- > From: Robert Sanderson [mailto:[log in to unmask]] > Sent: Monday, June 28, 2004 10:02 AM > To: [log in to unmask] > Subject: Unserializable scan response > > I've got a gateway to a Z39.50 server which returns characters which I > can't serialize to XML and/or successfully deserialize, for example the > ascii escape character. (Why this is in the index I have no idea, as it > makes the term impossible to search with, but that's not my problem or my > fault) > > As we don't have term surrogate diagnostics, what do I do? > > * Simply omit the term? > This seems wrong, but I'm tending towards it as the best of a bad lot. > > * Return a term with a null value? > Wrong, as a search for the null value may or may not produce results. > > * Strip out the unserializable characters and return the resulting term? > Seems wrong as the numberOfRecords will probably be wrong, barring good > fortune. > > * Other? > > Rob > > > ,'/:. Dr Robert Sanderson ([log in to unmask]) > ,'-/::::. http://www.o-r-g.org/~azaroth/ > ,'--/::(@)::. Special Collections and Archives, extension 3142 > ,'---/::::::::::. University of Liverpool > ____/:::::::::::::. > I L L U M I N A T I L5R Shop: http://www.cardsnotwords.com/