Markup Validation Service

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

1. Character Encoding mismatch!

   The character encoding specified in the HTTP header (utf-8) is different from the value in the <meta> element (iso-8859-1). I will use the value from the HTTP header (utf-8) for this validation.

Validation Output: 35 Warnings

Below is a list of the warning message(s) produced when checking your document.

1. Line 13, Column 5: NET-enabling start-tag requires SHORTTAG YES

   <br />Validation: <a href="http://validator.w3.org/detailed.html">W3C HTML

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

2. Line 18, Column 5: NET-enabling start-tag requires SHORTTAG YES

   <br /><a href="http://www.htmlhelp.com/tools/validator/">WDG

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

3. Line 24, Column 5: NET-enabling start-tag requires SHORTTAG YES

   <br /><a href="http://news.netcraft.com/">Netcraft.com</a>

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

4. Line 25, Column 5: NET-enabling start-tag requires SHORTTAG YES

   <br /><a href="http://www.htmlhelp.com/"><b>HTML Help</b> by the Web Design

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

5. Line 27, Column 5: NET-enabling start-tag requires SHORTTAG YES

   <br /><a href="http://www.webstyleguide.com/">Web Style Guide</a>

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

6. Line 29, Column 5: NET-enabling start-tag requires SHORTTAG YES

   <br /><a href="char.html"><b>My table of characters</b></a>&nbsp;

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

7. Line 31, Column 5: NET-enabling start-tag requires SHORTTAG YES

   <br /><a href="http://www.cs.tut.fi/~jkorpela/"><b>Character code</b>

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

8. Line 33, Column 5: NET-enabling start-tag requires SHORTTAG YES

   <br /><a

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

9. Line 38, Column 5: NET-enabling start-tag requires SHORTTAG YES

   <br /><b>Bad design</b>: Useit.com Top 10 Mistakes

   ✉

   For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

   This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

10. Line 41, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://web.mit.edu/guidelines.html">MIT: guidelines for

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

11. Line 43, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.x.org/">X.org Foundation</a>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

12. Line 44, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.weballey.net/">WEBalley, Web <b>publishing</b>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

13. Line 47, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.utoronto.ca/webdocs/HTMLdocs/NewHTML/">Introduction to

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

14. Line 49, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.math.uic.edu/~hanson/HTMLhelp.html">

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

15. Line 51, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.ocs.mq.edu.au/MIS/">Macquarie Univ. (Aus.) MIS</a>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

16. Line 52, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.unicode.org/charts/">Unicode, Inc. <b>Code 

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

17. Line 56, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://tlt.its.psu.edu/suggestions/international/bylanguage/">In…

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

18. Line 58, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://java.sun.com/docs/books/tutorial/">Java Tutorial</a>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

19. Line 60, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.apache.org/">Apache Software Foundation</a>,

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

20. Line 66, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="L-unix.php"><b>Unix</b></a>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

21. Line 67, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.openafs.org/"><b>Open AFS</b></a>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

22. Line 68, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><i><a href="L-misc.html">Misc.</a></i>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

23. Line 73, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="L-languages.php"><b>CSS, cascading style sheets</b></a>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

24. Line 79, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.weijers.net/setlang.php?comeback=/guide/">A

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

25. Line 85, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.netstrider.com/tutorials/HTMLRef/color/">HTML 

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

26. Line 87, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.e2.u-net.com/htaccess/make.htm">Pwd maker</a>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

27. Line 92, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://office.microsoft.com/pt-pt/default.aspx">MS Off.

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

28. Line 94, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />Microsoft: <a href="PptExample.ppt">PptExample</a>.ppt,

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

29. Line 98, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />PowerPoint: <a href=

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

30. Line 102, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.free-graphics.com/">Free-Graphics</a>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

31. Line 106, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />Colours:

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

32. Line 111, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.visibone.com/">Visibone</a>&nbsp;(<a href=

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

33. Line 115, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />Cadmus <a href="http://art.cadmus.com/da/">Digital Art</a>

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

34. Line 118, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><a href="http://www.w3.org/MarkUp/Guide/Style.html"

    ✉

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

↑ Top

Congratulations

The document located at <http://web.tecnico.ulisboa.pt/~mcasquilho/util/L-WWW.php> was successfully checked as HTML 4.01 Transitional. This means that the resource in question identified itself as "HTML 4.01 Transitional" and that we successfully performed a formal validation of it. The parser implementations we used for this check are based on OpenSP (SGML/XML).

"valid" Icon(s) on your Web page

To show your readers that you have taken the care to create an interoperable Web page, you may display this icon on any page that validates. Here is the HTML you could use to add this icon to your Web page:

  <p>
    <a href="http://validator.w3.org/check?uri=referer"><img
      src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01 Transitional" height="31" width="88"></a>
  </p>
  

A full list of icons, with links to alternate formats and colors, is available: If you like, you can download a copy of the icons to keep in your local web directory, and change the HTML fragment above to reference your local image rather than the one on this server.

Linking to this result

If you would like to create a link to this page (i.e., this validation result) to make it easier to revalidate this page in the future or to allow others to validate your page, the URI is <http://validator.w3.org/check?uri=http%3A%2F%2Fweb.tecnico.ulisboa.pt%2F~mcasquilho%2Futil%2FL-WWW.php;ss=1;verbose=1> (or you can just add the current page to your bookmarks or hotlist).

Validating CSS Style Sheets

If you use CSS in your document, you can check it using the W3C CSS Validation Service.

↑ Top

Source Listing

Below is the source input I used for this validation:

1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2. <html><head>
3. <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
4. <title>M&middot;Casquilho, IST: WWW, html, Unix</title>
5. <link rel="stylesheet" type="text/css"
6. href="http://web.tecnico.ulisboa.pt/~mcasquilho/commonstyle.css"></head>
7. <body class="sm">
8. <h3>Links: WWW, HTML, Unix</h3>
9. <table width="100%" class="sm">
10. <tr><td width="50%" valign="top">
11. <a href="http://www.w3.org/">World Wide Web Consortium</a> (<b>W3C</b>).
12. <a href="http://www.w3.org/Graphics/">Graphics</a>
13. <br />Validation: <a href="http://validator.w3.org/detailed.html">W3C HTML
14. <b>Val.</b> Service</a>,
15. <a href="http://jigsaw.w3.org/css-validator/">CSS</a>,
16. <a href="http://validator.w3.org/checklink/">link checker</a>
18. <br /><a href="http://www.htmlhelp.com/tools/validator/">WDG
19. HTML <b>Validator</b></a>,
20. &nbsp;<a href=
21. "http://www.anybrowser.org/campaign/abdesign3.html#validation">"Anybrowser"
22. t. &amp; <b>val.</b></a>
24. <br /><a href="http://news.netcraft.com/">Netcraft.com</a>
25. <br /><a href="http://www.htmlhelp.com/"><b>HTML Help</b> by the Web Design
26. Group</a>
27. <br /><a href="http://www.webstyleguide.com/">Web Style Guide</a>
28. (former Yale C/AIM)
29. <br /><a href="char.html"><b>My table of characters</b></a>&nbsp;
30. <a href="countrycodes.html"><b>Country</b> codes</a>
31. <br /><a href="http://www.cs.tut.fi/~jkorpela/"><b>Character code</b>
32. issues</a> (Helsinki Univ. of Techn.)
33. <br /><a
34. href="http://web.mit.edu/is/web/reference/guidelines/web.html">Special
35. HTML <b>Characters</b></a> (Academic Computing &nbsp;Support,
36. &nbsp;<a href="http://web.mit.edu/">MIT</a>)
38. <br /><b>Bad design</b>: Useit.com Top 10 Mistakes
39. <a href="http://www.useit.com/alertbox/990530.html">1999</a>,
40. <a href="http://www.useit.com/alertbox/designmistakes.html">2005</a>
41. <br /><a href="http://web.mit.edu/guidelines.html">MIT: guidelines for
42. <b>pages</b></a>
43. <br /><a href="http://www.x.org/">X.org Foundation</a>
44. <br /><a href="http://www.weballey.net/">WEBalley, Web <b>publishing</b>
45. for beginners</a>,
46. <a href="http://www.weballey.net/sins.html">mortal&nbsp;sins</a>
47. <br /><a href="http://www.utoronto.ca/webdocs/HTMLdocs/NewHTML/">Introduction to
48. <b>HTML</b></a> (Univ. of Toronto)
49. <br /><a href="http://www.math.uic.edu/~hanson/HTMLhelp.html">
50. <b>HTML</b> Tutorial HelpPage</a> (Univ. of Ill. at Chicago)
51. <br /><a href="http://www.ocs.mq.edu.au/MIS/">Macquarie Univ. (Aus.) MIS</a>
52. <br /><a href="http://www.unicode.org/charts/">Unicode, Inc. <b>Code
53. Charts</b></a>&nbsp; <a href="entities.html">entities</a>&nbsp;
54. <a href=
55. "http://www.av8n.com/computer/htm/encoding.htm">compatibly</A>&hellip;
56. <br /><a href="http://tlt.its.psu.edu/suggestions/international/bylanguage/">Info.
57. by language</a> (see Math)
58. <br /><a href="http://java.sun.com/docs/books/tutorial/">Java Tutorial</a>
59. (<a href="http://www.sun.com/"><i>Sun</i> Microsystems, Inc.</a>)
60. <br /><a href="http://www.apache.org/">Apache Software Foundation</a>,
61. <a href="http://httpd.apache.org/docs/1.3/mod/core.html">core</a>,
62. "<a href="http://httpd.apache.org/docs/1.3/mod/core.html#files">files</a>"
63. </td>
64. <td width="50%" valign="top"><a href="experiments.php">Some experiments</a>;
65. <a href="../var/test/">tests</a>
66. <br /><a href="L-unix.php"><b>Unix</b></a>
67. <br /><a href="http://www.openafs.org/"><b>Open AFS</b></a>
68. <br /><i><a href="L-misc.html">Misc.</a></i>
69. &bull;&nbsp;<a href="http://www.zdnet.com/devhead/">ZD Net</a>
70. &bull;&nbsp;<a href="L-languages.php"><b>Icons</b></a>
71. &bull;&nbsp;<a href="L-languages.php"><b>Javascript</b></a>
73. <br /><a href="L-languages.php"><b>CSS, cascading style sheets</b></a>
74. &bull;&nbsp;<a href="L-languages.php"><b>Excel</b></a>
75. &bull;&nbsp;<a href="L-languages.php"><b>Gnuplot</b></a>
76. &bull;&nbsp;<a href="L-languages.php"><b>Perl</b></a>
77. &bull;&nbsp;<a href="L-languages.php"><b>PHP</b></a>
79. <br /><a href="http://www.weijers.net/setlang.php?comeback=/guide/">A
80. guide to HTML</a>
81. &bull;&nbsp;<a href="http://www.alistapart.com/">A List Apart</a>
82. &bull;&nbsp;<a href="http://www.webreference.com/">WebReference</a>
83. &bull;&nbsp;<a href="http://www.webmonkey.com/">Webmonkey</a>
85. <br /><a href="http://www.netstrider.com/tutorials/HTMLRef/color/">HTML
86. Reference Guide</a> (Netstrider)
87. <br /><a href="http://www.e2.u-net.com/htaccess/make.htm">Pwd maker</a>
88. &bull;&nbsp;<a href="http://javascriptkit.com/">Javascript</a>
89. (passwd prot. ?)
90. &bull;&nbsp;<a href="http://www.thecgibin.com/">CGI-bin</a>,
91. &nbsp;<a href="http://grove.ufl.edu/cgi.shtml">Grove Fl.</a>
92. <br /><a href="http://office.microsoft.com/pt-pt/default.aspx">MS Off.
93. Design Gallery</a> (search)
94. <br />Microsoft: <a href="PptExample.ppt">PptExample</a>.ppt,
95. .<a href="PptExample.pps">pps</a>,
96. <a href="http://support.microsoft.com/default.aspx?
97. scid=kb;EN-US;q162059">Config. IE to open Off. docs</a>
98. <br />PowerPoint: <a href=
99. "http://www.ellenfinkelstein.com/powerpoint.html">E. Finkelstein</a>
100. &bull;&nbsp;<a href="http://www.infocomm.org/">infoComm</a>
101. (search Ellen Finkelstein)
102. <br /><a href="http://www.free-graphics.com/">Free-Graphics</a>
103. &bull;&nbsp;<a href="http://htmlgoodies.earthweb.com/">EarthWeb</a>
104. &bull;&nbsp;<a href="http://www.truquesedicas.com/">Truques</a> (tricks)
106. <br />Colours:
107. <a href="../var/colours/">my colours</a>;
108. <a href="http://www.lynda.com/hexh.html">lynda</a>;
109. <a href="https://www.w3schools.com/colors/colors_names.asp"
110. >w3schools</a> (colour names);
111. <br /><a href="http://www.visibone.com/">Visibone</a>&nbsp;(<a href=
112. "http://www.visibone.com/colorlab/">Colorlab</a>);
113. <a href=
114. "http://mega.ist.utl.pt/~mcasquil/misc/nondithering.html">nondithering</a>
115. <br />Cadmus <a href="http://art.cadmus.com/da/">Digital Art</a>
116. </td></tr>
117. </table>
118. <br /><a href="http://www.w3.org/MarkUp/Guide/Style.html"
119. >A touch of style</a> (W3C) (search "Named colors")
121. <table align="center" width="75%">
122. <tr><td bgcolor="black"><font size="-1" color="white">black</font></td>
123. <td bgcolor="silver"><font size="-1">silver</font></td>
124. <td bgcolor="gray"><font size="-1">gray</font></td>
125. <td bgcolor="white"><font size="-1">white</font></td>
126. <td bgcolor="maroon"><font size="-1" color="white">maroon</font></td>
127. <td bgcolor="red"><font size="-1" color="white">red</font></td>
128. <td bgcolor="purple"><font size="-1" color="white">purple</font></td>
129. <td bgcolor="fuchsia"><font size="-1">fuchsia</font></td></tr>
130. <tr><td bgcolor="green"><font size="-1">green</font></td>
131. <td bgcolor="lime"><font size="-1">lime</font></td>
132. <td bgcolor="olive"><font size="-1">olive</font></td>
133. <td bgcolor="yellow"><font size="-1">yellow</font></td>
134. <td bgcolor="navy"><font size="-1" color="white">navy</font></td>
135. <td bgcolor="blue"><font size="-1" color="white">blue</font></td>
136. <td bgcolor="teal"><font size="-1" color="white">teal</font></td>
137. <td bgcolor="aqua"><font size="-1">aqua</font></td></tr></table>
139. <div style="line-height: 6pt">&nbsp;</div>
140. <div style="line-height: 1.5pt; color: black;
141. background-color: red">&nbsp;</div>
143. <table width="100%" class="sm"><tr><td width="58"><a href=
144. "http://validator.w3.org/check?uri=
145. http://web.tecnico.ulisboa.pt/~mcasquilho/util/L-WWW.php;verbose=1;ss=1"><img
146. src="http://web.tecnico.ulisboa.pt/~mcasquilho/depot/valid-html401s.png"
147. alt="Valid HTML 4.01!" border="0" width="55" height="19"></a></td>
148. <td width="15%" align="left"><a href="http://www.ist.utl.pt"><img
149. src="http://web.tecnico.ulisboa.pt/~mcasquilho/depot/wwwist.png"
150. alt="IST" align="middle" border="0" width="156" height="34"></a></td>
151. <td width="70%" align=
152. "right"><i>http://web.tecnico.ulisboa.pt/~mcasquilho/util/L-WWW.php</i><br>
153. <i>Created:</i> ~1999 &mdash; <i>Last modified:</i>
154. 2017-10-29</td></tr></table>
155. </body></html>

↑ Top