W3C home > Mailing lists > Public > www-validator@w3.org > May 2005

Not Valid XHTML 1.0 Transitional

From: ~-V-~ <evan@indobara.com>
Date: Fri, 27 May 2005 17:04:57 +0700
To: webmaster@chip.co.my, www-validator@w3.org
Message-Id: <1117188297.4056.54.camel@lnxtpotc>


What is this...??

look that :
W3C QA Markup Validation Service
      * Skip Navigation | Home
      * About...
      * News
      * Docs
      * Help & FAQ
      * Feedback
      * Link Checker
Jump To: 
      * Results


XHTML 1.0 Transitional

Revalidate With Options 
Show Source
Parse Tree
....no attributes
Validate error pages
Verbose Output

Help on the options is available. 

The Validator XML support has some limitations. 
This page is not Valid XHTML 1.0 Transitional!
Below are the results of attempting to parse this document with an SGML

     1. Line 304, column 22: document type does not allow element
        "style" here
        <style type="text/css">
        The element named above was found in a context where it is not
        allowed. This could mean that you have incorrectly nested
        elements -- such as a "style" element in the "body" section
        instead of inside "head" -- or two elements that overlap (which
        is not allowed). 
        One common cause for this error is the use of XHTML syntax in
        HTML documents. Due to HTML's rules of implicitly closed
        elements, this error can create cascading effects. For instance,
        using XHTML's "self-closing" tags for "meta" and "link" in the
        "head" section of a HTML document may cause the parser to infer
        the end of the "head" section and the beginning of the "body"
        section (where "link" and "meta" are not allowed; hence the
        reported error). 
     2. Line 378, column 93: required attribute "alt" not specified
        ...ges/misc/top_header.gif" border="0" />
        The attribute given above is required for an element that you've
        used, but you have omitted it. For instance, in most HTML and
        XHTML document types the "type" attribute is required on the
        "script" element and the "alt" attribute is required for the
        "img" element. 
        Typical values for type are type="text/css" for <style> and
        type="text/javascript" for <script>. 
     3. Line 435, column 195: required attribute "alt" not specified
        ...ng" title="CHIP 05/2005 - Mei 2005" /></a>
     4. Line 444, column 203: required attribute "alt" not specified
        ...mages/cover/cover_cfvd_05_2005.png" /></a>
     5. Line 453, column 198: required attribute "alt" not specified
        ...itle="Computer Easy edisi Mei 2005" /></a>
     6. Line 462, column 110: required attribute "alt" not specified
        ...id/images/cover/cover_level_10.png" />
     7. Line 471, column 183: required attribute "alt" not specified
        ...cover/cover_chip_spesial_video.png" /></a>
     8. Line 476, column 80: character "&" is the first character of a
        delimiter but occurred as data
        ...lass="style1">CHIP Spesial: Notebook & PDA</div></td>
        If you wish to include the "<" character in your output, you
        should escape it as "&lt;". Another possibility is that you
        forgot to close quotes in a previous tag. 
     9. Line 480, column 105: character "&" is the first character of a
        delimiter but occurred as data
        ...der="1" title="CHIP Spesial Notebook & PDA"
    10. Line 480, column 186: required attribute "alt" not specified
        ...er/cover_chip_spesial_notebook.png" /></a>
    11. Line 539, column 4: end tag for "table" omitted, but OMITTAG NO
        was specified
        You may have neglected to close a tag, or perhaps you meant to
        "self-close" a tag; that is, ending it with "/>" instead of
    12. Line 502, column 0: start tag was here
        <table cellpadding="6" cellspacing="0" border="0" width="100%"
    13. Line 772, column 110: an attribute value specification must be
        an attribute value literal unless SHORTTAG YES is specified
        ...kel_Tom 2005 - Additional by <a
    14. Line 772, column 116: NET-enabling start-tag not immediately
        followed by null end-tag
        ...m 2005 - Additional by <a
    15. Line 772, column 141: end tag for element "a" which is not open
        ... href=http://www.nzboards.com>Kall</a></td>
        The Validator found an end tag for the above element, but that
        element is not currently open. This is often caused by a
        leftover end tag from an element that was removed during
        editing, or by an implicitly closed element (if you have an
        error related to an element being used where it is not allowed,
        this is almost certainly the case). In the latter case this
        error will disappear as soon as you fix the original problem. 
        If this error occured in a script section of your document, you
        should probably read this FAQ entry. 
    16. Line 803, column 97: cannot generate system identifier for
        general entity "refer"
        An entity reference was found in the document, but there is no
        reference by that name defined. Often this is caused by
        misspelling the reference name, unencoded ampersands, or by
        leaving off the trailing semicolon (;). The most common cause of
        this error is unencoded ampersands in URLs as described by the
        WDG in "Ampersands in URLs". 
        Entity references start with an ampersand (&) and end with a
        semicolon (;). If you want to use a literal ampersand in your
        document you must encode it as "&amp;" (even inside URLs!). Be
        careful to end entity references with a semicolon or your entity
        reference may get interpreted in connection with the following
        text. Also keep in mind that named entity references are case-
        sensitive; &Aelig; and &aelig; are different characters. 
        Note that in most documents, errors related to entity references
        will trigger up to 5 separate messages from the Validator.
        Usually these will all disappear when the original problem is
    17. Line 803, column 97: general entity "refer" not defined and no
        default entity
        This is usually a cascading error caused by a an undefined
        entity reference or use of an unencoded ampersand (&) in an URL
        or body text. See the previous message for further details. 
    18. Line 803, column 102: reference not terminated by REFC delimiter
        If you meant to include an entity that starts with "&", then you
        should terminate it with ";". Another reason for this error
        message is that you inadvertently created an entity by failing
        to escape an "&" character just before this text. 
    19. Line 803, column 102: reference to external entity in attribute
        This is generally the sign of an ampersand that was not properly
        escaped for inclusion in an attribute, in a href for example.
        You will need to escape all instances of '&' into '&amp;'. 
    20. Line 803, column 102: reference to entity "refer" for which no
        system identifier could be generated
        This is usually a cascading error caused by a an undefined
        entity reference or use of an unencoded ampersand (&) in an URL
        or body text. See the previous message for further details. 
    21. Line 803, column 96: entity was defined here
    22. Line 847, column 4: end tag for element "td" which is not open
    23. Line 848, column 4: end tag for element "tr" which is not open
    24. Line 850, column 6: "table" not finished but containing element
    25. Line 850, column 6: end tag for "table" omitted, but OMITTAG NO
        was specified
    26. Line 849, column 0: start tag was here
Valid XHTML 1.0! Feedback: The W3C Validator Team
Date: 2004/07/21 10:24:06  

Copyright © 1994-2004 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C
liability, trademark, document use and software licensing rules apply.
Your interactions with this site are in accordance with our public and
Member privacy statements. 
Received on Saturday, 28 May 2005 07:59:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 14:17:45 UTC