EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #08379
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Antwort: Re: perl module update introduced some trouble with entities
- To: <eprints-tech@ecs.soton.ac.uk>, David R Newman <drn@ecs.soton.ac.uk>
- Subject: [EP-tech] Antwort: Re: perl module update introduced some trouble with entities
- From: <martin.braendle@uzh.ch>
- Date: Tue, 1 Dec 2020 14:35:16 +0100
Hi Thomas,
there should be an entities.dtd file in [eprints_root]/lib/, maybe this is missing or entries are missing in it?
Also a phrase file should mention that in the
<!DOCTYPE phrases SYSTEM "entities.dtd">
definition right at the beginning after the XML declaration.
Kind regards,
Martin
--
Dr. Martin Brändle
Zentrale Informatik
Universität Zürich
Stampfenbachstr. 73
CH-8006 Zürich
"David
R Newman via Eprints-tech" ---01/12/2020 14:24:14---Hi Thomas, Named HTML entities are not supported in XML you need to use the decimal
Von: "David R Newman via Eprints-tech" <eprints-tech@ecs.soton.ac.uk>
An: <eprints-tech@ecs.soton.ac.uk>, <th.lauke@arcor.de>
Datum: 01/12/2020 14:24
Betreff: Re: [EP-tech] perl module update introduced some trouble with entities
Gesendet von: <eprints-tech-bounces@ecs.soton.ac.uk>
Hi Thomas,
Named HTML entities are not supported in XML you need to use the decimal code XML entity for ä which is ä
This is the same as needing to replace things like & and © with their equivalent decimal code XML entities.
Regards
David Newman
On 01/12/2020 12:00, th.lauke--- via Eprints-tech wrote:
CAUTION: This e-mail originated outside the University of Southampton.
Hi all,
any hint where to start digging for reason(s) after following error:
Failed to parse XML file: /usr/share/eprints/site_lib/lang/en/phrases/modified.xml: Entity: line 226: parser error : Entity 'auml' not defined
This error occurs after updating some perl modules ... :(
Is the 'bad' module already known?
What is more effective: Fixing the module (version) or the phrase file?
Thanks for any idea in advance
Thomas
*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: https://eur03.safelinks.protection.outlook.com/?url="">
*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url="">
|
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
- Follow-Ups:
- [EP-tech] Antwort: Re: perl module update introduced some trouble with entities
- From: <martin.braendle@uzh.ch>
- [EP-tech] Antwort: Re: perl module update introduced some trouble with entities
- References:
- Re: [EP-tech] eprints integration with office365 SMTP
- From: <th.lauke@arcor.de>
- [EP-tech] misconfigured or failed upgrade to 3.4.1?
- From: <th.lauke@arcor.de>
- [EP-tech] perl module update introduced some trouble with entities
- From: <th.lauke@arcor.de>
- Re: [EP-tech] perl module update introduced some trouble with entities
- From: David R Newman <drn@ecs.soton.ac.uk>
- [EP-tech] Antwort: Re: perl module update introduced some trouble with entities
- From: <martin.braendle@uzh.ch>
- Re: [EP-tech] eprints integration with office365 SMTP
- Prev by Date: Re: [EP-tech] perl module update introduced some trouble with entities
- Next by Date: Re: [EP-tech] Antwort: Re: perl module update introduced some trouble with entities
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):