Re: [WSG] Character Encoding Mismatch
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. 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 replied: Kristine, If your server is already specifying the character set (a.k.a. encoding) then you don't need to do so in your HTML. In fact, I'd recommend against doing so, ... The META tag is needed when serving the page from the hard drive - for example, when the page is saved for viewing later. (The hard drive does not send HTTP headers.) That's a good point that I should have mentioned, and I'm glad you brought it up. However, IMO this need is often overstated. Browsers are pretty good at guessing the encoding when they need to. I wouldn't rely on browsers guessing correctly for public pages, but I think the clutter of having duplicate encoding declarations usually outweighs the benefit. Of course, ideally one looks at one's pages using a local Web server. I think Windows Linux come with one preinstalled and I know that OS X does, so this should be within the reach of most folks. Cheers -- Philip http://NikitaTheSpider.com/ Whole-site HTML validation, link checking and more *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Character Encoding Mismatch
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 replied: Kristine, If your server is already specifying the character set (a.k.a. encoding) then you don't need to do so in your HTML. In fact, I'd recommend against doing so, ... The META tag is needed when serving the page from the hard drive - for example, when the page is saved for viewing later. (The hard drive does not send HTTP headers.) Cordially, David -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Character Encoding Mismatch
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 the header of your HTML should be a line like this - meta http-equiv=Content-Type content=text/html; charset=utf-8 /. Your server is sending an HTTP header that tells browsers to use the ISO-8859-1 character set, hence the mismatch. You can fix it by changing the line in your HTML to charset=iso-8859-1. However I always recommend instead using utf-8 because it's broader. ISO-8859-1 is actually a subset of utf-8. You'll have to talk to your server admin to change the HTTP header I believe. -Tim -- Tim Offenstein *** Campus Accessibility Liaison *** (217) 244-2700 CITES Departmental Services *** www.uiuc.edu/goto/offenstein *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Character Encoding Mismatch
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 http-equiv=content-type content=text/html; charset= iso-8859-1 / Best regards, Kepler Gelotte Neighbor Webmaster, Inc. 156 Normandy Dr., Piscataway, NJ 08854 http://www.neighborwebmaster.com www.neighborwebmaster.com phone/fax: (732) 302-0904 Thanks! *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***BEGIN:VCARD VERSION:2.1 N:Gelotte;Kepler;;Mr. FN:Kepler Gelotte ([EMAIL PROTECTED]) ORG:Neighbor Webmaster TITLE:Web Designer TEL;WORK;VOICE:(732) 302-0904 TEL;WORK;FAX:(732) 302-0904 ADR;WORK:;;156 Normandy Dr;Piscataway;NJ;08854;United States of America LABEL;WORK;ENCODING=QUOTED-PRINTABLE:156 Normandy Dr=0D=0APiscataway, NJ 08854=0D=0AUnited States of America URL;WORK:http://www.neighborwebmaster.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20070415T052107Z END:VCARD
RE: [WSG] Character Encoding Mismatch
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 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%2F Thanks! In the header of your HTML should be a line like this - meta http-equiv=Content-Type content=text/html; charset=utf-8 /. Your server is sending an HTTP header that tells browsers to use the ISO-8859-1 character set, hence the mismatch. You can fix it by changing the line in your HTML to charset=iso-8859-1. However I always recommend instead using utf-8 because it's broader. ISO-8859-1 is actually a subset of utf-8. You'll have to talk to your server admin to change the HTTP header I believe. -Tim -- Tim Offenstein *** Campus Accessibility Liaison *** (217) 244-2700 CITES Departmental Services *** www.uiuc.edu/goto/offenstein *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Character Encoding Mismatch
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 configuration of the Apache server. Unlikely to happen if other sites are hosted on server since it may negatively impact on other sites. An alternative would be to use a .htaccess file. if the administrators allow you to do this. Info on this approach is available at http://www.w3.org/International/questions/qa-htaccess-charset Andrew On Sat, April 5, 2008 6:52 am, Kepler Gelotte 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 Change this tag in your head section: meta http-equiv=content-type content=text/html; charset=utf-8 / To: meta http-equiv=content-type content=text/html; charset= iso-8859-1 / Best regards, Kepler Gelotte Neighbor Webmaster, Inc. 156 Normandy Dr., Piscataway, NJ 08854 http://www.neighborwebmaster.com www.neighborwebmaster.com phone/fax: (732) 302-0904 Thanks! *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Andrew Cunningham Research and Development Coordinator Vicnet State Library of Victoria Australia [EMAIL PROTECTED] *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Character Encoding Mismatch
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 set (a.k.a. encoding) then you don't need to do so in your HTML. In fact, I'd recommend against doing so, and the problem you've experienced is exactly why. If you specify the encoding in two (or more) places, they can get out of synch. You might *think* you're specifying ISO-8859-1 because that's what your HTML META tag says, but if the server says something else, that's what takes priority. It's important to understand that the encoding tells browsers (and other user agents, like Googlebot) how to interpret non-ASCII characters in your page. It's a common mistake to think that these are restricted to accented characters that we generally don't use in English, but content pasted in from Microsoft Word (for instance) is likely to contain non-ASCII as well. In other words, you might be using them without realizing it. If you are, and you get the encoding wrong, then what you see as quote marks (for instance) might look like this to others: †Whatever tool you're using to save files should give you a choice of which encoding/character set to use. You can use ISO-8859-1 to write in English and most Western European languages. Since your Web server is already identifying your pages as such, it might be a good choice. Others have suggested UTF-8 which can represent anything under the sun. That's great, but you'll have to find some way to cajole your server into telling the world that your pages are UTF-8, not ISO-8859-1. If you can't, you'll have to stick to the latter. -- Philip http://NikitaTheSpider.com/ Whole-site HTML validation, link checking and more *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Character encoding mismatch
Hi Richard, Thanks for that info, the guy who runs the server here has fixed the server to run UTF-8, so no problems there. The XHTML reference was really good. I had started using the apos; XHTML tag for #39; not realising that it wouldn't work for browsers that don't read XHTML (such as IE5). Glad I got to read that one before we went live! I have now changed it to rsquo; What's your opinion on using Character Entities over Hexadecimal values. I can't seem to get a clear response on which is better. Thanks again. Paul - Original Message - From: Richard 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' information in .htaccess"http://www.w3.org/International/questions/qa-htaccess-charsetThat would allow you to continue using utf-8, which I think is a good move.Also, you may find the following useful wrt using character references:"Using character entities and NCRs"http://www.w3.org/International/questions/qa-escapesHope that helps,RIRichard IshidaInternationalization LeadW3Chttp://www.w3.org/People/Ishida/http://www.w3.org/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 mismatch 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 explain this in simple terms?? Have a look at the material in W3Cs internationalization-Section W3C I18N Topic Index http://www.w3.org/International/resource-index.html#charset I like the Tutorial: Character sets encodings in XHTML, HTML and CSS http://www.w3.org/International/tutorials/tutorial-char-enc/#choosing At least they try to explain the rather complicated stuff for everyone. ;-) HTH Susanne -- http://sujag.de - Webentwicklung und -beratung [EMAIL PROTECTED] Lottumstr. 22, 10119 Berlin, Tel: 030 - 440 483 47 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** **The discussion list for http://webstandardsgroup.org/See http://webstandardsgroup.org/mail/guidelines.cfmfor some hints on posting to the list getting help**
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' information in .htaccess http://www.w3.org/International/questions/qa-htaccess-charset That would allow you to continue using utf-8, which I think is a good move. Also, you may find the following useful wrt using character references: Using character entities and NCRs http://www.w3.org/International/questions/qa-escapes Hope that helps, RI Richard Ishida Internationalization Lead W3C http://www.w3.org/People/Ishida/ http://www.w3.org/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 mismatch 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 explain this in simple terms?? Have a look at the material in W3Cs internationalization-Section W3C I18N Topic Index http://www.w3.org/International/resource-index.html#charset I like the Tutorial: Character sets encodings in XHTML, HTML and CSS http://www.w3.org/International/tutorials/tutorial-char-enc/# choosing At least they try to explain the rather complicated stuff for everyone. ;-) HTH Susanne -- http://sujag.de - Webentwicklung und -beratung [EMAIL PROTECTED] Lottumstr. 22, 10119 Berlin, Tel: 030 - 440 483 47 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Character encoding mismatch
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 value from the HTTP header (iso-8859-1) for this validation. ... and so on. 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 explain this in simple terms?? The problem is not with your XHTML but with your server. Most likely you are running Apache with AddDefaultCharset in configuration. If you have access to httpd.conf you should just comment out this directive, or change it to utf-8. Regards, Rimantas ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Character encoding mismatch
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 PROTECTED] wrote: 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 value from the HTTP header (iso-8859-1) for this validation. -- My header code looks like this, which should validate fine: !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en head titletitle/title meta http-equiv=Content-Type content=text/html; charset=utf-8;/ I have just started reading more about character encoding and special characters, is my problem that I have used decimal character refereces? For example - as #45; ' as #39; and so on. 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 explain this in simple terms?? Cheers ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Character encoding mismatch
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 explain this in simple terms?? Have a look at the material in W3Cs internationalization-Section W3C I18N Topic Index http://www.w3.org/International/resource-index.html#charset I like the Tutorial: Character sets encodings in XHTML, HTML and CSS http://www.w3.org/International/tutorials/tutorial-char-enc/#choosing At least they try to explain the rather complicated stuff for everyone. ;-) HTH Susanne -- http://sujag.de - Webentwicklung und -beratung [EMAIL PROTECTED] Lottumstr. 22, 10119 Berlin, Tel: 030 - 440 483 47 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Character encoding mismatch
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 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 value from the HTTP header (iso-8859-1) for this validation and so on. 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 explain this in simple terms??The problem is not with your XHTML but with your server. Most likelyyou are running Apache with AddDefaultCharset in configuration. If youhave access to httpd.conf youshould just comment out this directive, or change it to utf-8.Regards,Rimantas**The discussion list for http://webstandardsgroup.org/See http://webstandardsgroup.org/mail/guidelines.cfmfor some hints on posting to the list getting help**
Re: [WSG] Character encoding mismatch
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: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 explain this in simple terms??Have a look at the material in W3Cs internationalization-SectionW3C I18N Topic Indexhttp://www.w3.org/International/resource-index.html#charsetI like the Tutorial: Character sets encodings in XHTML, HTML and CSShttp://www.w3.org/International/tutorials/tutorial-char-enc/#choosingAt least they try to explain the rather complicated stuff for everyone. ;-)HTHSusanne-- http://sujag.de - Webentwicklung und -beratung[EMAIL PROTECTED]Lottumstr. 22, 10119 Berlin, Tel: 030 - 440 483 47**The discussion list for http://webstandardsgroup.org/See http://webstandardsgroup.org/mail/guidelines.cfmfor some hints on posting to the list getting help**
Re: [WSG] Character Encoding Mismatch
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. This simplest way to match them would be changing your meta tags. 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? -- Kay Smoljak http://kay.smoljak.com * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Character Encoding Mismatch
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: http://www.w3.org/International/tutorials/tutorial-char-enc/Overview.html#declaring cite * An in-document encoding allows the document to be read correctly when not on a server. This applies not only to static documents read from disk or CD, but also dynamic documents that are saved by the reader. * An in-document declaration of this kind helps developers, testers, or translation production managers who want to perform a visual check of a document. /cite When using a xml-declaration, the encoding should go there, and not in a meta-tag. /AndersN * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Character Encoding Mismatch
...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 the answer, but: Some servers can be configured to set the HTTP header from the meta http-equiv or examining the first few bytes of the document. In the case of server or configuration limitations, the meta http-equiv can provide user agents with the encoding. From http://www.w3.org/TR/REC-html40/charset.html#h-5.2.2 quote ...conforming user agents must observe the following priorities when determining a document's character encoding (from highest priority to lowest): 1. An HTTP charset parameter in a Content-Type field. 2. A META declaration with http-equiv set to Content-Type and a value set for charset. 3. The charset attribute set on an element that designates an external resource. /quote -ben * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Character Encoding Mismatch
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 seems to work 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. This simplest way to match them would be changing your meta tags. Or, depending on your web server setup, use a .htaccess file: http://httpd.apache.org/docs/mod/core.html.en#adddefaultcharset AddDefaultCharset On should do according to the docs... grtz Vincent -- Vincent De Baere * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Character Encoding Mismatch
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 sent. That's why inn PHP, if you're playing with the headers there can't be so much as a blank space befor the ?php. And here's the meta tag: meta http-equiv=Content-Type content=text/html; charset=iso-8859-1 / Notice it says http-equiv, as in only equivlant, but not the real thing. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Character Encoding Mismatch
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 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. This simplest way to match them would be changing your meta tags. Implications? Check Anne van Kesteren's (of 10 Questions fame: http://webstandardsgroup.org/features/anne-van-kesteren.cfm ) Quick Guide to UTF-8 http://annevankesteren.nl/archives/2004/06/utf-8 If you're really keen, you can find out more about specifying the character encoding at: http://www.w3.org/TR/REC-html40/charset.html#h-5.2.2 - ben * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
