EPrints Technical Mailing List Archive
Message: #08515
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Elements-EPrints Odd Characters stopping upload
- To: <eprints-tech@ecs.soton.ac.uk>, James Kerwin <jkerwin2101@gmail.com>
- Subject: Re: [EP-tech] Elements-EPrints Odd Characters stopping upload
- From: David R Newman <drn@ecs.soton.ac.uk>
- Date: Wed, 17 Feb 2021 10:31:28 +0000
Hi James,
I think you would need to look at this field in the Elements
record in its database to look how it is being stored differently
when there is an import compared to where there is manual entry.
As you said I think the problem is in part that text box entries
get parsed and encoded before going into the database but imports
do not (or at very least the process between input and output to
the Elements database is different). It would be useful to know
how they look different in the Elements database as they may
assist making EPrints more resilient to unexpected encodings in
future.
However "\\x{2019}" looks like an escaped version of something
that is not particularly valid. If this was "\\u{2019}" this
would probably work better as \x I think can only be used to
represent a standard ASCII character that can be only two hex
digits like \x3a is a colon ":". \u is used for the extended
character set (i.e. UTF-16). \u{2019} in UTF-8 would be
\xE2\x80\x99.
It would be interesting to get a bit more information about your other issue with regular quote marks and semi-colons that are part of the standard ASCII set rather than an extended characters. These really should not be causing a problem.
Regards
David Newman
CAUTION: This e-mail originated outside the University of Southampton.Hi All,
This is an Elements/EPrints question. Apologies that it isn't purely EPrints, but this is probably the best place to get an answer. I want to know if others experience this or it's some oddity to our setup.
We are using RT1 (for now) and EPrints 3.3.14 (also for now until upgrade). Occasionally we get an Elements record that is from Scopus, PubMed etc. that has an odd character in it that prevents upload. When I look in the Apache logs it tells me the problem. Yesterday's one was the presence of:
"Unicode Character “’” (U+2019)"
Which showed in the logs as:
"Can't escape \\x{2019}, try uri_escape_utf8() instead at /opt/eprints3/perl_lib/URI/Escape.pm"
Importantly if I copy the problem characters to the manual elements record it doesn't pose a problem. There appears some processing to properly encode characters entered via text box, but not characters dragged in from other sources into Elements.
I've also had the issue with the files containing "'" or" ";" etc not being accessible via Elements (a very similar, but different problem).
I found where I COULD fix the former issue, but it involves changing EPrints code when I SHOULD be altering the Symplectic connector code on the repo server.
Anyway, I'm not specifically looking for a solution, but has anybody else experienced anything similar? If so, does it stop with RT2? I hope to raise a ticket with Symplectic over this eventually.
Thanks,James
*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/
- References:
- [EP-tech] Elements-EPrints Odd Characters stopping upload
- From: James Kerwin <jkerwin2101@gmail.com>
- [EP-tech] Elements-EPrints Odd Characters stopping upload
- Prev by Date: [EP-tech] search filter to show only the last version
- Next by Date: Re: [EP-tech] search filter to show only the last version
- Previous by thread: [EP-tech] Sort view with creators_name and corp_creators
- Index(es):