[ipac] Illegal XML char in items out?

[Jonathan Rochkind]

I don't know why it pasted into the email message with the <>, I'm not 
sure what that's about. But removing the weird em-dash from the call 
number does seem to solve the problem. In the staff client itself, there 
are no <> marks, actually. I think they were an artifact of my email 
client somehow.

Man, char encoding is confusing.

I guess it's good to know that any weird char in a MARC record can 
completely bring HIP to it's knees. Not very encouraging, but good to know.

Jonathan

Jason Stephenson wrote:
> Jonathan Rochkind wrote:
>   
>> It's in a call number. The call number looks like this:
>> QH365.D22 O69 1859 [1964] <QH365.D22%20O69%201859%20%5B1964%06%5D>
>>     
>
> Actually, I think your problem is the < and > around the call number.
>
> As Natasha reported, we see this all the time. It is nearly always 
> caused by a foreign language character in a bib or authority record. The 
> offending entry almost always has a unicode or utf-8 character 
> surrounded by < and >. The XSLT sees those angle brackets and attempts 
> to transform that "tag" into another. Since it fails to look that tag 
> up, it just bombs. (This analysis is pure speculation, however removing 
> the offending diacritic from the authority or bib always fixes the problem.)
>
> Cheers,
> Jason
> _______________________________________________
> ipac mailing list
> ipac at lists.tblc.org
> http://lists.tblc.org/mailman/listinfo/ipac
>
>   

-- 
Jonathan Rochkind
Sr. Programmer/Analyst
The Sheridan Libraries
Johns Hopkins University
410.516.8886 
rochkind (at) jhu.edu