The Fix XHTML Syntax Errors Feature

Are Syntax Errors Blurring the Way Browsers Display Your Site?

Today’s Web browsers decide how content or indexes appear based on Web Standards. Unrecognizable pages are bound to happen despite a developer’s best efforts.

The Solution

Use this feature to correct many syntactical and structural errors in XHTML and ASP.NET pages. Doing so decreases validation errors and warnings, while maintaining the desired rendering behavior.

This specific feature assumes the structure of the document is correct. The Fix XHTML Syntax Errors feature focuses on fixing common errors and malpractices. That is why we recommend using other Aggiorno feature to help you correct any validation issues first.

Fix malformed entities

XHTML entities should always begin with an & and end with a ; character. Some browsers render them even when they are not correctly defined, which leads to inconsistencies.

Replace characters with entities

Non-standard characters such as á, ñ or @ should be defined using named or numerical entities, not directly using the underlying encoding.

Depending on what value you choose, encodable entities will be represented using a numbered (select Numbered Entities option) or a named (select Named Entities option) XHTML-based representation.

This feature is valuable when pasting code from an external source, such as a word processor, and when writing content using a WYSIWYG code editor. Type it as usual and tell Aggiorno to convert characters to entities in a snap.

Enclose attributes' values in quotes

Attribute values should always be surrounded by single or double quotes. Some browsers do not enforce this restriction, but the results aren’t predictable. This feature eliminates the risk by correctly quoting all values.

Turn attributes into lowercases

To simplify page processing and reduce potential ambiguity, XHTML requires that all attributes be in lower case. This feature detects and transforms all capitalized attribute names to lower case.

Lowercase tags

Even though most browsers ignore this, XHTML technically requires lower case tags. Failure to comply with this standard is reason enough for an XHTML page to be declared a non-valid XHTML Web page.

Use default attribute value

When an attribute does not have an assigned value, most browsers use its default value. However, XHTML requires that attributes be assigned explicit values.