On Sun, Apr 6, 2008 at 12:11 AM, David Hucklesby [EMAIL PROTECTED] wrote:
On Fri, Apr 4, 2008 at 4:16 PM, Kristine Cummins
[EMAIL PROTECTED] wrote:
Can someone tell me how to fix this W3C warning – I'm new to
understanding this part.
On Fri, Apr 4, 2008 at 4:16 PM, Kristine Cummins
[EMAIL PROTECTED] wrote:
Can someone tell me how to fix this W3C warning – I'm new to understanding
this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
On Fri, 4 Apr 2008 20:15:19 -0400, Nikita The Spider
Can someone tell me how to fix this W3C warning - I'm new to understanding
this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
Thanks!
***
List Guidelines:
At 1:16 PM -0700 4/4/08, Kristine Cummins wrote:
Can someone tell me how to fix this W3C warning - I'm new to
understanding this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2Fhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
Thanks!
In
Can someone tell me how to fix this W3C warning - I'm new to understanding
this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
Change this tag in your head section:
meta http-equiv=content-type content=text/html; charset=utf-8 /
To:
meta
FIXED. The URL below will not show any warnings now.
Thanks again.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Tim Offenstein
Sent: Friday, April 04, 2008 1:42 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Character Encoding Mismatch
At 1:16 PM -0700 4/4/08, Kristine
The advice below is sufficient if your content is limited to characters in
the ISO-8859-1 repertoire If you are using any characters outside this
repertoire on the site, then i wouldn't use this approach.
As
indicated in a previous email, you could ask your web master to change the
default
On Fri, Apr 4, 2008 at 4:16 PM, Kristine Cummins
[EMAIL PROTECTED] wrote:
Can someone tell me how to fix this W3C warning – I'm new to understanding
this part.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.beverlywilson.com%2F
Kristine,
If your server is already specifying the character
Ishida
To: wsg@webstandardsgroup.org
Sent: Tuesday, November 22, 2005 6:54
PM
Subject: RE: [WSG] Character encoding
mismatch
Thanks, Susan, for pointing to that stuff.Paul, you if
you're using Apache you may also find this particularly useful:"Setting
'charset' inform
/International/
http://people.w3.org/rishida/blog/
http://www.flickr.com/photos/ishida/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susanne Jäger
Sent: 10 November 2005 12:21
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Character encoding
I am getting the followingwarningwhen I
validate my pages:
--
Character Encoding mismatch!
The character encoding specified in the HTTP header
(iso-8859-1) is different from the value in the
meta element (utf-8). I will use the value
from the HTTP header
2005/11/10, Paul Collins [EMAIL PROTECTED]:
I am getting the following warning when I validate my pages:
--
Character Encoding mismatch!
The character encoding specified in the HTTP header (iso-8859-1) is
different from the value in the meta element (utf-8). I will use the
Instead of:
meta http-equiv=Content-Type content=text/html; charset=utf-8;/
Try:
meta http-equiv=Content-Type content=text/html; charset=iso-8859-1 /
This will match what your web server is sending, otherwise change your
web server config if you can :-)
Lloyd
On 11/10/05, Paul Collins [EMAIL
Paul Collins wrote, On 10.11.2005 12:44:
I thought this was the correct way to add special
characters for XHTML, but what I am reading now seems to contradict
this. This is the part of standards where I get a bit confused. Does
anyone have any advice or know of some good articles where they
That seems to work, thanks heaps
Rimantas
- Original Message -
From:
Rimantas
Liubertas
To: wsg@webstandardsgroup.org
Sent: Thursday, November 10, 2005 12:01
PM
Subject: Re: [WSG] Character encoding
mismatch
2005/11/10, Paul Collins [EMAIL PROTECTED]:
I
Thanks Susanne, that's a really good
reference.
Cheers,Paul
- Original Message -
From:
Susanne Jäger
To: wsg@webstandardsgroup.org
Sent: Thursday, November 10, 2005 12:21
PM
Subject: Re: [WSG] Character encoding
mismatch
Paul Collins wrote, On 10.11.2005 12
On Fri, 2 Jul 2004 13:03:34 +1000, Ben Bishop [EMAIL PROTECTED] wrote:
Your web server (eg Apache) sends the character encoding HTTP header.
In order to match up your HTTP header to your meta-equiv you would
need to make the change server-side, something you might not have
access to do.
Kay Smoljak wrote:
I was under the impression - please correct me if I'm wrong - that if
the server is sending the character encoding, there is no need to also
have the meta tag. Is there any other reason to include it,
client-side?
Take a look at:
...if the server is sending the character encoding...Is there
any other reason to include it, client-side?
ominous toneDid you read the W3C link posted?/ominous tone ;)
I can't speak with any authority on this matter, and not meaning to
break the unwritten rule of not answering unless you know
On Friday 02 July 2004 05:03, Ben Bishop wrote:
Hi Sage,
When I validate my page, I get the following message
The character encoding specified in the HTTP header (utf-8) is
different from the value in the meta element (iso-8859-1).
I'd like to keep the iso-8859-1 value, just because it
When I validate my page, I get the following message (which doesn't
invalidate the page, but I still want to fix it):
The character encoding specified in the HTTP header (utf-8) is
different from the value in the meta element (iso-8859-1). I will
use the value
Sage Olson wrote:
Here's my header:
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
That's not you HTTP header. The HTTP headers are sent by the server
before even the first byte of your document is
Hi Sage,
When I validate my page, I get the following message
The character encoding specified in the HTTP header (utf-8) is
different from the value in the meta element (iso-8859-1).
I'd like to keep the iso-8859-1 value, just because it seems to work
Your web server (eg Apache) sends the
23 matches
Mail list logo
