Technical Advisory Service
2001 - 2004 archive
Compliance corner comprises a series of issues that have arisen in the context of projects meeting technical standards. This page covers:
Another frequent cause of non-compliance is the failure to identify a character encoding in every text document on a website. Browsers need to know your pages' character encoding (or "charset") in order to display correctly the characters used in its content. Without the correct character encoding a browser may not manage the conversion in to the correct characters for your pages.
Best practice is to identify the character encoding in use either
in the HTTP header or within the <HEAD> section of the document. To identify
the character encoding in the HTTP header you will need access to the web server.
If this is not possible, placing the character encoding in the <HEAD>
section is also allowed and will override the content of any HTTP header if
such is present.
Choice of Character Sets
You are reminded that the technical Standards and Guidelines were updated in February 2002 to state that any standard character set is now permissible.
TIP: indicate the actual character encoding your project is using when filling out your quarterly progress report.
See Character encodings at:
For further information see Character Encoding at:
Return to Compliance Corner contents
|UKOLN is funded by MLA, the Museums, Libraries and Archives Council, the Joint Information Systems Committee (JISC) of the Higher and Further Education Funding Councils, as well as by project funding from the JISC and the European Union. UKOLN also receives support from the University of Bath where it is based.|
T A S : 2 0 0 1 - 2 0 0 4 : A R C H I V E
This page is part of the NOF-digi technical support pages http://www.ukoln.ac.uk/nof/support/.
The Web site is no longer maintained and is hosted as an archive by UKOLN.
Page last updated on Monday, May 09, 2005