W3C home > Mailing lists > Public > www-validator-cvs@w3.org > January 2007

[Bug 4214] Unknown Parse Mode! and Namespace Found in non-XML Document

From: <bugzilla@wiggum.w3.org>
Date: Sat, 13 Jan 2007 02:54:02 +0000
CC:
To: www-validator-cvs@w3.org
Message-Id: <E1H5Z1u-0005oL-Op@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4214

           Summary: Unknown Parse Mode! and Namespace Found in non-XML
                    Document
           Product: Validator
           Version: HEAD
          Platform: PC
               URL: http://www.mutah.com/v3/index.html
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Parser
        AssignedTo: link@pobox.com
        ReportedBy: ali.m.zaidi@gmail.com
         QAContact: www-validator-cvs@w3.org


Hi,

I am trying to develop a page using XHTML Basic 1.1.

When I check the above page I get the following results page:
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.mutah.com%2Fv3%2Findex.html

With these errors coming up:


Unknown Parse Mode!

    The MIME Media Type (text/html) for this document is used to serve both
SGML and XML based documents, and it is not possible to disambiguate it based
on the DOCTYPE Declaration in your document. Parsing will continue in SGML
mode.
Namespace Found in non-XML Document

    Namespace "" found, but document type is not XML!

This page is not Valid -//W3C//DTD XHTML Basic 1.1//EN!

Below are the results of attempting to parse this document with an SGML parser.

   1. Error Line 6 column 220: character data is not allowed here.

      ...classifieds and extensive library!" />

      You have used character data somewhere it is not permitted to appear.
Mistakes that can cause this error include putting text directly in the body of
the document without wrapping it in a container element (such as a
<p>aragraph</p>) or forgetting to quote an attribute value (where characters
such as "%" and "/" are common, but cannot appear without surrounding quotes).


Is this a bug? Or Am I doing something wrong?

Thanks.
Received on Saturday, 13 January 2007 02:54:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:27 UTC