Trick Builder: Difference - HTML and XHTML

When inserting codes into the Blogger template, page element, or blog post, you may have seen error messages that the code could not be parsed, was not well-formed, was broken, or that the elements were not closed properly. These errors can be corrected if you understand the rules that must be adhered to in XHTML documents. Blogger templates use the XHTML 1.0 Strict Document Type. In this article, we shall explain some of the XHTML syntax or rules, so that you may troubleshoot and resolve the problems if these error messages should occur.
XML, HTML and XHTML
We shall keep this short. Just so as you understand what we said about document type, view the Page Source or Source of your Blogger blog. You should see this document type declaration at the very top:-
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The terms – XML, HTML and XHTML - refer to the markup language used to write the web pages. Many of us would have heard of HTML (Hypertext Markup Language), invented by Tim Berners-Lee, and used since the early days of internet. XML (Extensible Markup Language) is a meta-language, used to create other markup languages. The traditional HTML was later recast to use the rules of XML and that resulted in a new XML application, called XHTML (Extensible Hypertext Markup Language). Because XHTML rules are strict and unforgiving, not conforming to them when attempting to modify the template would result in error messages. So, what are these rules that Bloggers like us should take note of?

Basic Rules of XHTML

1. Codes to be in lowercase
Since XML is case sensitive, all the element keywords and attribute names used in XHTML should be in the lowercase. For example, the template code is not this:-
Tips for New Bloggers

but this:-
Tips for New Bloggers

If you have noticed, the elements and attribute names between the lesser than (<) and greater than (>) signs have to be in the lowercase. However, the value, which in this case is “Tips for New Bloggers”, can be in the uppercase, lowercase, or mixed case.

2. Attribute values to be in quotation marks
All the attribute values have to be enclosed either in single or double quotation marks. The following examples are not accepted by XHTML:-

Text Link

Instead, they should be written as such:-

3. Container elements must have closing tags
This is not correct:-
A paragraph.

In XHTML, there must be a closing tag with a forward slash (/) at the end:-

A paragraph.

Examples of the many non-empty elements that have opening and corresponding closing tags are:-

...

...

...

...

...

...

...

...

...

4. Standalone elements to be closed
Some of the elements are empty or standalone. They do not have associated closing tags. Common examples are:-

Nonetheless, in XHTML, these elements must be terminated or closed. There are two ways to do that. One way to terminate the element is to put a forward slash (/) at the end like this:-

The second way is to add a corresponding closing tag like this:-

...

...
...
...

...
...
...

5. Elements to be properly nested
This means that elements must be closed in the reverse order. For example, this code is not accepted in XHTML:-

...

It is improperly nested because the form was created first followed by the table. To close them in the proper order, the table must be closed before the form, like this:-
...

6. Document to have only one root element
In the XHTML document, you will see that except for the document type declaration, all the codes are nested between and . This is the root element and all other elements or sub elements are in between. The document structure will look like this:-

...
...

7. Attribute minimization is not allowed
In XHTML, all attributes should be in the form name="value". Even if the value is the same as the name, it cannot be minimized to one word. Hence, in our Add Text Box and Textarea article, the textarea code is not this:-
Hyperlink Code

but this:-
Hyperlink Code

XHTML Character Entities
Quite a number of readers had asked why they were unable to display HTML codes in their blog posts or why their codes were not well-parsed when inserted into the template. If you have noticed by now, the codes are wrapped in the lesser than (<) and greater than (>) signs. The moment these are posted, they will be interpreted as codes and will trigger an action by the browser. Should you want to display these as part of the text, use their character entities instead.
" "
& &
< <
> >

The next time you see an error message to the effect that the code is not well formed, not well parsed, not properly closed, etc., take a look at this guide, troubleshoot the problem and try out the possible solutions.