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. > >>

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. >> >> On Fri, 4 Apr 2008 20:15:19 -0400, Nikita T

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. > Kristine, If your server is already specifying the ch

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 conf

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

RE: [WSG] Character Encoding Mismatch

> Can someone tell me how to fix this W3C warning - I'm new to understanding this part. > Change this tag in your section: To: Best regards, Kepler Gelotte Neighbor Webmaster, Inc. 156 Normandy Dr.,

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

[WSG] Character Encoding Mismatch

Can someone tell me how to fix this W3C warning - I'm new to understanding this part. Thanks! *** List Guidelines: http://webstandardsgroup.org/mail/guideli

Re: [WSG] Character encoding mismatch

--- 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:"Setti

RE: [WSG] Character encoding mismatch

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@we

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 PROTEC

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

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 the

Re: [WSG] Character encoding mismatch

Instead of: Try: 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

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 element (utf-8). I will use the

[WSG] Character encoding mismatch

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 element (utf-8). I will use the value from the HTTP header (iso-8859-1)

RE: [WSG] Character encoding

TED] On Behalf Of Joshua Street > Sent: 04 June 2005 03:52 > To: Web Standards Group mailing list > Subject: [WSG] Character encoding > > I've always thought that characters should be marked up with > appropriate entity codes (for example, accented letters, > etc.) in

Re: [WSG] Character encoding

Vaska.WSG wrote: For some reason, I feel I have to escape every character that is not a letter or number. I was feeling the same, and working on it, when this thread arrived. At the time it appeared I was looking up numeric entity lists in Cyrillic and adapting them to a conversion_map fun

Re: [WSG] Character encoding

For some reason, I feel I have to escape every character that is not a letter or number. I was feeling the same, and working on it, when this thread arrived. At the time it appeared I was looking up numeric entity lists in Cyrillic and adapting them to a conversion_map function (for PHP). I

Re: [WSG] Character encoding (HTML Tidy)

Gene Falck wrote: Tidy is one of the programs I have been thinking of getting, so I would like to hear about any bugs and bug fixes. Regards, Gene Falck Tidy has evolved from it's beginning with Dave Raggett. Like many tools, it's great when you learn how to use it, and to work with it's

Re: [WSG] Character encoding

Hi Geoff, You wrote: ... I know I have developed sites in the past that I have felt pretty confident have been a good attempt at best of practice, but age sure shows their vintage, and I am not talking about the CSS, just thinking of the (X)HTML. LOL--that's quite nice compared to what I th

Re: [WSG] Character encoding

Hi Matt You wrote: Lea, I'm not sure why I always escape the dash - perhaps because I can??? :) I am assuming the dash will someday cause me problems, so I just escape it now, to avoid a lot of re-work. I don't expect an unescaped dash to cause trouble as it has, AFAIK, no meanings in code.

Re: [WSG] Character encoding

On Sat, 4 Jun 2005 18:56:16 -0500, Matt Thommes wrote: > For some reason, I feel I have to escape every character that is not a > letter or number. OK, I'm always up for new Best Practices, but I do need some basis for adopting changes. I escape double quotes and ampersands because of the HTML is

Re: [WSG] Character encoding

At 04:36 PM 6/4/2005, Lea de Groot wrote: On Sat, 4 Jun 2005 18:07:48 -0500, Matt Thommes wrote: > For instance, I always escape a dash (-) with –--- when > using it in a normal sentence. Thats interesting - I escape such entities as ampersands (&) and double quotes ("), but not things such

Re: [WSG] Character encoding

>> What benefits or problems avoided do you perceive by doing this and >> what other characters are you escaping? > > Lea, I'm not sure why I always escape the dash - perhaps because I can??? > :) > While preparing my recent post about image replacement I was playing with fangs and noticed that I

Re: [WSG] Character encoding

Matt Thommes wrote: What benefits or problems avoided do you perceive by doing this and what other characters are you escaping? Lea, I'm not sure why I always escape the dash - perhaps because I can??? :) I am assuming the dash will someday cause me problems, so I just escape it now, to

Re: [WSG] Character encoding

> What benefits or problems avoided do you perceive by doing this and > what other characters are you escaping? Lea, I'm not sure why I always escape the dash - perhaps because I can??? :) I am assuming the dash will someday cause me problems, so I just escape it now, to avoid a lot of re-work.

Re: [WSG] Character encoding

On Sat, 4 Jun 2005 18:07:48 -0500, Matt Thommes wrote: > For instance, I always escape a dash (-) with –--- when > using it in a normal sentence. Thats interesting - I escape such entities as ampersands (&) and double quotes ("), but not things such as hyphens. What benefits or problems avoid

Re: [WSG] Character encoding

I've always thought that characters should be marked up with appropriate entity codes... It's just always felt dirty seeing certain characters not written in their appropriate entity codes. Eh, maybe on anglo-saxon websites... The rest of the world has a different opinion ;) -- Jan Brasna aka

Re: [WSG] Character encoding

Josh, I am also torn with this issue. I ALWAYS escape characters with their decimal values, as Vlad suggests, even if I am serving up UTF-8. However, within code snippets (), I don't make as much of an effort - for whatever reason. For instance, I always escape a dash (-) with –--- when usin

Re: [WSG] Character encoding

On Fri, 2005-06-03 at 23:42 -0400, Vlad Alexander wrote: > Hi Joshua, > > If you are serving your content as Unicode (UTF-16 or UTF-8), then there is > no need to use entities. If you do need to escape characters and you are > using XHTML, then it's best to use their decimal values rather than e

Re: [WSG] Character encoding

Hi Joshua, If you are serving your content as Unicode (UTF-16 or UTF-8), then there is no need to use entities. If you do need to escape characters and you are using XHTML, then it's best to use their decimal values rather than entities. This makes your markup more easily parsable by XML techno

[WSG] Character encoding

I've always thought that characters should be marked up with appropriate entity codes (for example, accented letters, etc.) in (X)HTML, rather than simply pasted in and left for character encoding and the user agent to take care of. I've written a plugin for the WordPress weblog software that does

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 element (iso-8859-1). > > I'd like to keep the iso-8859-1 value, just becau

Re: [WSG] Character Encoding Mismatch

> ...if the server is sending the character encoding...Is there > any other reason to include it, client-side? Did you read the W3C link posted? ;) 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

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:

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. >

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 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

Re: [WSG] Character Encoding Mismatch

Sage Olson wrote: Here's my header: http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";> 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

[WSG] Character Encoding Mismatch

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 element (iso-8859-1). I will use the value from th