EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #01991

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: [FIX] missing entities

Hi Tim,

I use Ubuntu in a VirtualBox for dev, and this cropped up at some point after I upgraded to 13.04. All of my messages disappeared, and I eventually went in and replaced the &nbsp; !

G

-----Original Message-----
From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Tim Brody
Sent: 03 June 2013 12:57
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Re: [FIX] missing entities

Hi Graham,

That's news to me that Ubuntu has a problem with this? The specific bug is a regression in a RedHat patch - which has never appeared in the core
libxml2 library.

If you're thinking about "xmllint" you need to provide a path to the entities file *and* enable external file loading.

--
All the best,
Tim.

On Mon, 2013-06-03 at 09:30 +0100, Graham Triggs wrote:
> Tim,
> 
> Ubuntu has also been caught out by the same issue.
> 
> The real issue here is that &nbsp; is not a defined entity reference 
> in XML. LibXML is doing the correct thing when it refuses to read the 
> XML file.
> 
> The phrases file should be updated to either replace the &nbsp; 
> references with &#160; or an entity declaration needs to be added to 
> the file:
> 
> <!ENTITY nbsp   "&#160;">
> 
> 
> Regards,
> G
> 
> -----Original Message-----
> From: eprints-tech-bounces@ecs.soton.ac.uk 
> [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Tim Brody
> Sent: 31 May 2013 11:22
> To: eprints-tech@ecs.soton.ac.uk
> Subject: [EP-tech] [FIX] missing entities
> 
> Hi All,
> 
> For those of you running RHEL 6 I've uploaded patched libxml2 packages
> here:
> http://files.eprints.org/851/
> 
> Based on a patch supplied to the bugzilla ticket:
> https://bugzilla.redhat.com/show_bug.cgi?id=863166
> 
> Hopefully RHEL will release an official update soon ...
>