EPrints has many configuration files in XML format. Often these may be edited to include special characters, such as ampersand (&), copyright and accented character. To reduce the chances sysadmins maintaining EPrint repositories hitting this issue standard template, phrase, citation and workflow files should have their own enitities.dtd for defining special characters like this.
The text was updated successfully, but these errors were encountered:
This looks to already be in place for all core phrase and template files. The eprints-tech list issue reported by Thomas Lauke may have been due to a historical issue before this was set up or use of an HTML entity in a citation or workflow file where entities.dtd is not specified.
EPrints has many configuration files in XML format. Often these may be edited to include special characters, such as ampersand (&), copyright and accented character. To reduce the chances sysadmins maintaining EPrint repositories hitting this issue standard template, phrase, citation and workflow files should have their own enitities.dtd for defining special characters like this.
The text was updated successfully, but these errors were encountered: