W3C home > Mailing lists > Public > www-amaya@w3.org > October to December 2000

Re: Document encoding or undefined...

From: Irene VATTON <Irene.Vatton@inrialpes.fr>
Date: Mon, 13 Nov 2000 16:12:28 +0100
Message-Id: <200011131512.QAA19932@tahiti.inrialpes.fr>
To: "W. Jeffrey Rankin" <jrankin@jeffr.net>
cc: www-amaya@w3.org
> I'm getting a document encoding error in the log file under NT and Solaris
> 8 with all the pages at http://www.jeffr.net/.
> 
> I added this line to my index.html as a test:
> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
> 
> It doesn't seem to make a difference. The HTML and CSS validate OK, so I 
> wonder what's going on?

It works if you add it in the xml declaration:
<?xml version="1.0" encoding="iso-8859-1"?>

The encoding must be known before starting the parsing. It's why 
Amaya says that there is no defined encoding when the information is given by a
tag META.
We're now adding code that looks for meta elements to get the encoding before
starting the parsing.
In the next release your declaration:
<meta http-equiv="Content-Type" content="text/html; charset="iso-8859-1" />
should work
-- 
     Irene.
Received on Monday, 13 November 2000 10:12:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 September 2007 14:24:27 GMT