Eric and David, thank you both for the advice, it was really helpful and I've fixed my problem.
It appears that a script a colleague wrote as part of the EPrints software made use of a UTF8 module, but only on one field of the data where it's ussually necessary. In this instance it was on a name field which doesn't typically require it. thanks again for the advice; it's greatly appreciated. James On Tue, Nov 13, 2018 at 2:49 PM David Spector < david...@springtimesoftware.com> wrote: > James Kerwin, > > When strange characters cause HTTP error 500, this is usually caused by > a mismatch in specified character encoding. Make sure that your form > page and your Apache configuration file both specify the same encoding. > For most of the world, the current standard encoding is called "utf-8". > Make sure all of your HTML and other Web files, and your Apache > configuration file (httpd.conf or other name) all specify the encoding > "utf-8". Then most of the world's languages can be used without problem. > > David Spector > Springtime Software > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
