Can't Find a Character Encoding Line that Satisfies W3C Validator

Discussion in 'HTML & Website Design' started by Darden12, Jan 26, 2011.

  1. #1
    I'm trying to get a Web page of mine to "pass muster" with the W3C Validator at

    http://validator.w3.org

    Every time I submit the page, I get the following error message:

    Warning No Character Encoding Found! Falling back to UTF-8.

    I don't know why I'm getting this message because I've already taken the corrective steps outlined on websites, namely, I've added the following line to the HEAD section on my HTML:

    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

    After that didn't help, I even followed another suggestion and added this line to my .htacess file:

    AddType 'text/html; charset=ISO-8859-1' html

    Neither change satisfied the Validator, which is still returning the same error message:

    Warning No Character Encoding Found! Falling back to UTF-8.



    Any ideas what the W3C is looking for that I'm not doing?

    Thanks.
     
    Darden12, Jan 26, 2011 IP
  2. Dodger

    Dodger Peon

    Messages:
    1,494
    Likes Received:
    60
    Best Answers:
    0
    Trophy Points:
    0
    #2
    What is the document type, Html or XHtml? If the former, you need to remove the closing slash at the end of the META.

    Also, where did you put that declaration? It should reside inside the HEAD section.

    Were there any other errors related to the document type or head? If so, what were they?
     
    Dodger, Jan 26, 2011 IP
  3. buddyborg

    buddyborg Guest

    Messages:
    36
    Likes Received:
    1
    Best Answers:
    0
    Trophy Points:
    0
    #3
    i don't use the validator. changing from simple tools to really complicated stuff, we all know how often the specifications change.
    I recall learning google maps one time. and 6 months later there was v3. i recall being proud of my actionscript 2 toolbox...
    I work with Dojo for my webpages. None of them will ever validate because Dojo objects use custom attributes.

    browsers are too buggy to please anyway. i could be completely wrong in this posting and in my web development habits. i'm sure many will disagree and say that validation by w3c is very important. i suppose it depends on the the critical degree, and the scope of your project. I work on little things geared towards smaller audiences.
    Seeing frustration at yet another checkpoint in the development process is....frustrating....
     
    buddyborg, Jan 27, 2011 IP
  4. AtSeaDesign

    AtSeaDesign Active Member

    Messages:
    172
    Likes Received:
    2
    Best Answers:
    1
    Trophy Points:
    93
    #4
    Follow Dodger's advice. Is the first line in the code a DOCTYPE?
     
    AtSeaDesign, Jan 27, 2011 IP
  5. Dodger

    Dodger Peon

    Messages:
    1,494
    Likes Received:
    60
    Best Answers:
    0
    Trophy Points:
    0
    #5
    Don't you just love it when somebody has a problem, it is like pulling teeth to get information from them?
     
    Dodger, Jan 27, 2011 IP