Skip to content
View in the app

A better way to browse. Learn more.

Web Designer Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Checking for Coding Errors

Featured Replies

I am trying to check my site, http://www.strongfamilies.us, for coding errors using http://validator.w3.org. However, this site states the following:

 

--------

No Character Encoding Found! Falling back to windows-1252.

 

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 "windows-1252" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents. Before defaulting to windows-1252 the validator also tried to read the content with the following encoding(s), without success: UTF-8.

 

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

 

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.

---------------------

 

I read through the tutorial yet I cannot figure out how to add the necessary coding needed for this site to check for errors. If someone could help me with this, I would surely appreciate it. Thanks.

Adding

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

above your Meta Tags in the <head> section should sort this out.

 

Also you are using too many keywords, you will need to reduce this massively or you will actually rank lower in search engines. A dozen or so should be sufficient.

  • Author

Thanks for your response. I just entered the code you recommended on http://www.strongfamilies.us/participantreg.php:

 

<head>

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

<title>The "Standing Up To Bullying" Conference</title>

<meta name="description" content="Introducing the latest research, this bullying conference is designed to empower educators with skills to eradicate school bullying and violence.">

<meta name="keywords" content=......

 

and I get Sorry! This document can not be checked when checking with http://validator.w3.org. More specifically, this site is reporting:

 

Sorry, I am unable to validate this document because on line 229 it contained one or more bytes that I cannot interpret as utf-8 (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.

The error was: utf8 "\x94" does not map to Unicode.

 

I have no idea what this means. Please advice. Thanks. Also, thanks for your keyword recommendation.

You're using weird double quote marks for the last 2 testimonials. Just re-type them using your keyboard.

 

This same problem was the reason for the warning in your first post. You need to flush the site code of any strange, non UTF-8 characters you've cut and paste from other applications/websites.

  • Author

I found the right character code to use that http://validator.w3.org accepts. However, it seems that this site is giving me a lot of false negative readings. It lists about 114 errors on one page. Many of the errors have to do with the use of < and >. When I remove either of these characters, the whole page goes high-wire. I'm really confused about this validation site!

I found the right character code to use that http://validator.w3.org accepts. However, it seems that this site is giving me a lot of false negative readings. It lists about 114 errors on one page. Many of the errors have to do with the use of < and >. When I remove either of these characters, the whole page goes high-wire. I'm really confused about this validation site!

 

If you use < then a browser thinks that it has to start some processing. If you want the < to appear as text and not start processing you must use the character code < and > for the >

 

Utf-8 will raise validation errors so replace with code from here

http://www.tedmontgomery.com/tutorial/HTMLchrc.html

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.