RE: I think I have the solution to the errors.

[Robert Orosz <roboro@auto-trol.com>]

Stuart,

You got it.

The http-equiv attribute is absolutely required. It causes an HTTP server to
create the specified header in the HTTP response. This is what the W3C
validator is looking for.

Rob

-----Original Message-----
From: Galt, Stuart A [mailto:stuart.a.galt@boeing.com]
Sent: Wednesday, April 29, 2009 7:33 AM
To: Robert Orosz; David Cruikshank
Cc: Lofton Henderson
Subject: I think I have the solution to the errors.


Hello all,

I have played around with the validator a bit more and have come to a
few
conclusions.

addin the line <?xml.... at the top of the file turns it from html
transitional 
into xhtml.  I think that we have not made the jump to xhtml so this
line should 
be removed.  I actually started reading
http://www.w3.org/International/O-charset
a bit more closely and discovered that the way I was doing it with the
xml
declaration at the top has problems see:
http://www.w3.org/International/articles/serving-xhtml/#declaration

So the correct solution is to not have a xml declaration (it isn't
xml....)
and to have a meta tag that looks like:

<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1" >
or
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" >

The reason it didn't work with my original meta tag was because I didn't
have the http-equiv="Content-Type" attribute included.  Once I added the
attribute
and deleted the xml declaration the file validated 
- when I used "by file upload" in internet exploder
- when I used "by file upload" in firefox
- when I used "by direct input" in firefox

Any thoughts?

--
Stuart Galt
SGML Resource Group
stuart.a.galt@boeing.com
(206) 544-3656

<<application/ms-tnef>>