Lee Passey wrote:
It appears that the file is latin-1 encoded, despite the fact that the DTD claims that it is utf-8 encoded. This caused Firefox some grief as it tried to utf-8-decode some latin-1 accented vowels.
That is just what Apache thinks it is because it doesn't look inside the file before serving it. Apache can be made to serve the encoding based on the file extension. Lacking a definite extension it will serve the default which is iso-8859-1. The same problem exists with all plain text files in the archive. They are all served as iso-8859-1. We cannot fix that unless we rename all files: 12345-8.txt --> 12345-8.txt.8 12345-0.txt --> 12345-0.txt.0 In this case Apache sees the .0 extension, strips it, and serves the file as 12345-0.txt with utf-8 encoding. And don't look at me. I made this suggestion before the new filesystem went live.
I grabbed an arbitrary "tei.css" style sheet off the net, and added the line:
<?xml-stylesheet href="tei.css" type="text/css"?>
You can also include an XSL stylesheet which gives you far more power. But why do you want to look at the TEI file in the browser when there is an HTML file available? -- Marcello Perathoner webmaster@gutenberg.org