4 Years
Discussion Span
Last Post by JorgeM

also I did a markup validation and it said this:

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

    None of the standards sources gave any information on the character encoding labeling for this document. Without encoding information it is impossible to reliably validate the document. As a fallback solution, the "UTF-8" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents.

    Read the FAQ entry on character encoding for more details and pointers on how to fix this problem with your document.

    Info No Character encoding declared at document level

    No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

    See this tutorial on character encoding for techniques and explanations.

If you are starting to develop this site, why not go with an HTML5 Doctype? This doesnt mean that you have to include new elements introducted in HTML5.

The HTML5 page structure is as follows...

<!DOCTYPE html>
<html lang="en">
    <meta charset="utf-8" />
    <title>Example document</title>
    <link href="stylesheet.css" rel="stylesheet"/>
    <script src="script.js"></script>
    <p>Example paragraph</p>

Ok, so I took a look at the source code of your website. My first suggestion to you is to clean up your page structure.

For example, you didnt close the <head> element. You didnt include the <body> element and didnt close the <html> element either.

This is going to cause different browsers to render the page differently. Browsers will try to render the elements as best they can, but it is best to follow standards.

In your case, if you are trying to apply a strict doctype, these things that I mentioned are very important.

again, I would suggest to you look at the sample structure that I provided earlier. I didnt see any specific HTML5 elements on your page so the structure I provided will work perferctly and be supported accross the different browsers.

Edited by JorgeM


Just taking a quick peek, you're using the HTML 5 Enabler for IE which searches the body of the document for HTML 5 tags. You never actually end the page header and start the body so the script has nothing to search hence why it won't convert your HTML 5 tags in IE



The reference to the HTML5Shiv on that page is not being used. The DOCYTPE is not set for HTML5, and there are no HTML5 elements on the page. If you read the previous posts, the OP is not interested in the HTML5 structure, but I was suggesting that since the page can be easily fixed and be HTML5 compliant and ready.


All I had to do is add a <body> tag and that did it. Thanks JorgeM for pointing that out.



He is using the <nav> tag for his navigation menu which is an HTML 5 element and is only supported in IE9 and the HTML5Shiv is being used for earlier versions of IE. In the end we made the same suggestion I just didn;t refresh the page after looking at his code so I didn't see you had provided the same answer prior to me

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.