[ipac] Illegal XML char in items out?

[Jonathan Rochkind]

Okay, responding to my own message, I managed to track down the 
offending char. [For future reference, I added &GetXML=1 to the end of 
the URL---and then Firefox reported it couldn't render the XML, and 
actually gave me a char location, which the xml.log error wasn't giving me!]

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>

It's that last em-dash char after 1964, which may or may not even show 
up on your monitor. It's showing up for me right now in Thunderbird 
(although it does really funny things when I try and cut and paste it), 
but when I try to paste it into my text editor, it shows up as blank. It 
DOES show up in Horizon client. It's some kind of weird em-dash? Or just 
a normal em-dash, instead of a -?  Whatever it is, Saxon doesn't want to 
render it, which is causing the 'items out' page to crash. 
<QH365.D22%20O69%201859%20%5B1964%06%5D>

Anyone have any advice, run into anything like this before, have any 
idea what's going on? I'm about to go talk to my catalogers, but 
wondering if any other systems people have run into this before. I'm not 
sure how Horizon staff client deals with non-ascii chars, to even figure 
out how this char got in there, or even what char it actually IS!

Jonathan

Jonathan Rochkind wrote:
> When a particular patron clicks on their 'items out' link in HIP (3.08), 
> they get only a message There is a problem with the XSLT. Check XSL 
> Server for errors.
>
> I have no reproduced this in my test server so I can try and debug. 
> Checking the xsl.log tells me:
>
> Mar 26 10:36:07 [XSLProcessor:transformUsingSaxon] 
> javax.xml.transform.Transform
> erException: org.xml.sax.SAXParseException: illegal XML character U+6
>
>
> Hmm, is this a char that Saxon doesn't like in my actual item title or 
> something? I'm going to look at the actual items to try and identify it.
>
> But has anyone run into this before? Any workaround?
>
> I need to find a pristine copy of whatever the relevant XML file is, to 
> put in and make sure the error is reproducible with that, instead of our 
> customized searchresponse.xml, before reporting this to SD. I have no 
> idea what is the relevant XML file, or if I even still have it around. 
> Sigh. If anyone wants to send me a .zip'd copy of pristine HIP 3.08 xml/ 
> directory, that would be very helpful.
>
> Jonathan
> _______________________________________________
> 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