<dl id="warnings">

<TMPL_IF NAME="W01">
  <dt id="W01">Missing "<code>charset</code>" attribute for
    "<code><TMPL_VAR NAME="W01_ct" ESCAPE="HTML"></code>" document.</dt>
  <dd>
    <p>
      The HTTP <code>Content-Type</code> header
      (<code><TMPL_VAR NAME="W01_ct" ESCAPE="HTML"></code>) sent by your web
      <TMPL_IF NAME="W01_upload">browser<TMPL_ELSE>server</TMPL_IF>
      (<code><TMPL_VAR NAME="W01_agent" ESCAPE="HTML"></code>) did not contain
      a "<code>charset</code>" parameter, but the Content-Type was one of
      the XML <code>text/*</code> sub-types.
    </p>
    <p>
      The relevant specification
      (<a href="http://www.ietf.org/rfc/rfc3023.txt">RFC 3023</a>)
      specifies a strong default of "<code>us-ascii</code>" for
      such documents so we will use this value regardless of any encoding you
      may have indicated elsewhere.
    <p>
      If you would like to use a different encoding, you should arrange to have
      your <TMPL_IF NAME="W01_upload">browser<TMPL_ELSE>server</TMPL_IF> send
      this new encoding information.
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W02">
  <dt id="W02">No Character Encoding Found!</dt>
  <dd>
    <p>
      Falling back to
      "<code><TMPL_VAR NAME="W02_charset" ESCAPE="HTML"></code>"
      (<a href="docs/users.html#fbc">explain...</a>).
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W03">
  <dt id="W03">Character Encoding Override in effect!</dt>
  <dd>
    <p>
      The detected character encoding
      "<code><TMPL_VAR NAME="W03_use" ESCAPE="HTML"></code>"
      has been suppressed and
      "<code><TMPL_VAR NAME="W03_opt" ESCAPE="HTML"></code>" used instead.
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W04">
  <dt id="W04">No Character Encoding Found!
    <TMPL_IF NAME="W04_override">
      Using
    <TMPL_ELSE>
      Falling back to 
    </TMPL_IF>
    <code><TMPL_IF NAME="W04_charset"><TMPL_VAR NAME="W04_charset" ESCAPE="HTML"><TMPL_ELSE>UTF-8</TMPL_IF></code>.
  </dt>
  <dd>
  <TMPL_IF NAME="W04_override">
    <p>I was not able to extract a character encoding labeling from any of
      the valid sources for such information. I will use the character 
      encoding <code><TMPL_IF NAME="W04_charset"><TMPL_VAR NAME="W04_charset" ESCAPE="HTML"><TMPL_ELSE>UTF-8</TMPL_IF></code>,
      which you have chosen via the <code>Encoding</code> override option, for 
      tentative validation. 
    </p>
  <TMPL_ELSE>
    <p>
      I was not able to extract a character encoding labeling from any of
      the valid sources for such information. Without encoding information
      it is impossible to reliably validate the document. I'm falling back
      to the "<code><TMPL_IF NAME="W04_charset"><TMPL_VAR NAME="W04_charset" ESCAPE="HTML"><TMPL_ELSE>UTF-8</TMPL_IF></code>" 
      encoding and will attempt to perform the validation,
      but this is likely to fail for all non-trivial documents.
    </p>
  </TMPL_IF>
  <TMPL_IF NAME="opt_verbose">
    <p>The sources I tried to find encoding information include:</p>
    <ul>
      <li>The HTTP Content-Type field.</li>
      <li>The XML Declaration.</li>
      <li>The HTML "META" element.</li>
    </ul>
    <p>
      And I even tried to autodetect it using the algorithm defined in
      <a href="http://www.w3.org/TR/REC-xml#sec-guessing">Appendix F of
        the XML 1.0 Recommendation</a>.
    </p>
    <p>
      Since none of these sources yielded any usable information, I will not be
      able to reliably validate this document. Sorry. Please make sure you
      specify the character encoding in use.
    </p>
    <p class="note">
      Specifying a character encoding is normally done in the web server
      configuration file or administration program. The <a
        href="http://www.w3.org/"><abbr
          title="World Wide Web Consortium">W3C</abbr></a> <a
        href="http://www.w3.org/International/"><abbr
          title="Internationalization">I18N</abbr> Activity</a> has collected
        <a href="http://www.w3.org/International/O-HTTP-charset"
           title="A Few Tips On How To Specify The Character Encoding">a few
          tips on how to do this</a> in popular web server implementations.
    </p>
    <TMPL_INCLUDE NAME="iana_charset_blurb.tmpl">
    <p>
      To quickly check whether the document would validate after addressing
      the missing character encoding information, you can use the "Encoding"
      form control earlier in the page to force an encoding
      override to take effect. "iso-8859-1" (Western Europe and North America)
      and "utf-8" (Universal, but not commonly used in legacy documents) are
      common encodings if you are not sure what encoding to choose.
    </p>
  <TMPL_ELSE>
    <p>Read the <a href="docs/help.html#faq-charset"><acronym title="Frequently Asked Questions">FAQ</acronym> 
    entry on character encoding</a> for more details and pointers on how to fix this problem with your document.</p>
  </TMPL_IF>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W05">
  <dt id="W05"><code>DOCTYPE</code> Override in effect!</dt>
  <dd>
    <p>
      Any DOCTYPE Declaration in the document has been suppressed and the
      DOCTYPE for "<code><TMPL_VAR NAME="W05_dtd" ESCAPE="HTML"></code>"
      inserted instead. The document will not be Valid until you alter the
      source file to reflect this new DOCTYPE.
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W06">
  <dt id="W06">Unable to Determine Parse Mode!</dt>
  <dd><p>Falling back to SGML mode.</p></dd>
</TMPL_IF>
<TMPL_IF NAME="W07">
  <dt id="W07">Contradictory Parse Modes Detected!</dt>
  <dd>
    <p>
      The MIME Media Type
      (<code><TMPL_VAR NAME="W07_mime" ESCAPE="HTML"></code>) indicated parse
       mode should be <TMPL_VAR NAME="W07_ct" ESCAPE="HTML">, but the
       <code>DOCTYPE</code> Declaration indicates
       <TMPL_VAR NAME="W07_dtd" ESCAPE="HTML"> mode.  Using
       <TMPL_VAR NAME="W07_ct" ESCAPE="HTML"> mode based on the
       <code>Content-Type</code> header.
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W08">
  <dt id="W08">Unknown Parse Mode!</dt>
  <dd>
    <p>
      The MIME Media Type
      (<code><TMPL_VAR NAME="W08_mime" ESCAPE="HTML"></code>) for this
      document is used to serve both SGML and XML based documents, 
      and it is not possible to disambiguate it 
      based on the <code>DOCTYPE</code> Declaration in your document. Parsing
      will continue in SGML mode.
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W09">
  <dt id="W09">No <code>DOCTYPE</code> found! Attempting validation with <TMPL_VAR NAME="W09_dtd" ESCAPE="HTML">.</dt>
  <dd>
    <p>
      The DOCTYPE Declaration was not recognized or is missing. This
      probably means that the Formal Public Identifier contains a spelling
      error, or that the Declaration is not using correct syntax. Validation
      has been performed using a default "fallback" Document Type Definition
      that closely resembles "<TMPL_VAR NAME="W09_dtd" ESCAPE="HTML">", but the
      document will not be Valid until you have corrected this problem with the
      DOCTYPE Declaration.
    </p>
    <TMPL_IF NAME="opt_verbose">
    <p>
      You should place a DOCTYPE declaration as the very first thing in your
      HTML document. For example, for a typical <a
      href="http://www.w3.org/TR/xhtml1/">XHTML 1.0</a> document:
    </p>
    <pre>
      &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&gt;
      &lt;html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"&gt;
        &lt;head&gt;
          &lt;title&gt;Title&lt;/title&gt;
        &lt;/head&gt;

        &lt;body&gt;
          &lt;!-- ... body of document ... --&gt;
        &lt;/body&gt;
      &lt;/html&gt;
    </pre>
    <p>
      For XML documents, you may also wish to include an "XML Declaration"
      even before the DOCTYPE Declaration, but this is not well supported
      in older browsers. More information about this can be found in the
      <a href="http://www.w3.org/TR/xhtml1/">XHTML 1.0</a> Recommendation.
    </p>
      <p>
        The W3C QA Activity maintains a <a
          href="http://www.w3.org/QA/2002/04/valid-dtd-list.html">List of
            Valid Doctypes</a> that you can choose from, and the <acronym
          title="Web Design Group">WDG</acronym> maintains a document on
        "<a href="http://htmlhelp.com/tools/validator/doctype.html">Choosing
           a DOCTYPE</a>".
      </p>
  <TMPL_ELSE>
    <p>Learn <a href="docs/help.html#faq-doctype">how to add a doctype to your document</a> 
    from our <acronym title="Frequently Asked Questions">FAQ</acronym>.</p>
  </TMPL_IF>

  </dd>
</TMPL_IF>
<TMPL_IF NAME="W10">
  <dt id="W10">Unknown Namespace Found</dt>
  <dd>
    <p>
      Unknown namespace "<code><TMPL_VAR NAME="W10_ns" ESCAPE="HTML"></code>"
      for <TMPL_VAR NAME="W10_type" ESCAPE="HTML"> document!
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W11">
  <dt id="W11">Namespace Found in non-XML Document</dt>
  <dd>
    <p>
      Namespace "<code><TMPL_VAR NAME="W11_rns" ESCAPE="HTML"></code>" found,
      but document type is not XML!
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W12">
  <dt id="W12">No Namespace Found</dt>
  <dd>
    <p>
      No Namespace was found, but document type requires one to be present!
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W13">
  <dt id="W13"><code>DOCTYPE</code> Override in effect!</dt>
  <dd>
    <p>
      The detected DOCTYPE Declaration
      "<code><TMPL_VAR NAME="W13_org"></code>" has been
      suppressed and the DOCTYPE for
      "<code><TMPL_VAR NAME="W13_new" ESCAPE="HTML"></code>" inserted instead,
      but even if no errors are shown below the document will not be Valid
      until you update it to reflect this new DOCTYPE.
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W14">
  <dt id="W14">No <code>DOCTYPE</code> Found!</dt>
  <dd>
    <p>
      Falling back to HTML 4.01 Transitional.
      (<a href="docs/users.html#fbd">explain...</a>)
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W15">
  <dt id="W15"><code>DOCTYPE</code> Override in effect!</dt>
  <dd>
    <p>
      The DOCTYPE Declaration for "<TMPL_VAR NAME="W15_dtd" ESCAPE="HTML">"
      has been inserted at the start of the document, but even if no errors
      are shown below the document will not be Valid until you add the new
      DOCTYPE Declaration.
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W16">
  <dt id="W16">No DOCTYPE Found! Falling Back to
    <TMPL_VAR NAME="W16_dtd" ESCAPE="HTML">.</dt>
  <dd>
    <p>
      A DOCTYPE Declaration is mandatory for most current markup languages
      and without one it is impossible to reliably validate this document.
      I am falling back to "<TMPL_VAR NAME="W16_dtd" ESCAPE="HTML">" and will
      attempt to validate the document anyway, but this is very likely to
      produce spurious error messages for most non-trivial documents.
    </p>
  <TMPL_IF NAME="opt_verbose">
    <TMPL_INCLUDE NAME="doctype_spiel.tmpl">
    <p>
      The W3C QA Activity maintains a <a
        href="http://www.w3.org/QA/2002/04/valid-dtd-list.html">List of
          Valid Doctypes</a> that you can choose from, and the <acronym
        title="Web Design Group">WDG</acronym> maintains a document on
      "<a href="http://htmlhelp.com/tools/validator/doctype.html">Choosing
         a DOCTYPE</a>".
    </p>
  <TMPL_ELSE>
    <p>
      So what should I do?
      <a href="docs/help.html#faq-doctype">Tell me more...</a>
    </p>
  </TMPL_IF>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W17">
  <dt id="W17">No Character Encoding detected!</dt>
  <dd>
    <p>
      To ensure correct validation, processing, and display, it is important
      that the character encoding is properly labeled.
      <a href="http://www.w3.org/International/O-charset.html">More
      information...</a>
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W18">
  <dt id="W18">Character Encoding mismatch!</dt>
  <dd>
    <p>
      The character encoding specified in the HTTP header
        (<code><TMPL_VAR NAME="W18_http" ESCAPE="HTML"></code>)
      is different from the value in the XML declaration
        (<code><TMPL_VAR NAME="W18_xml" ESCAPE="HTML"></code>).
      I will use the value from the HTTP header
        (<code><TMPL_VAR NAME="W18_use" ESCAPE="HTML"></code>).
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W19">
  <dt id="W19">Character Encoding mismatch!</dt>
  <dd>
    <p>
      The character encoding specified in the HTTP header
        (<code><TMPL_VAR NAME="W19_http" ESCAPE="HTML"></code>)
      is different from the value in the <code>&lt;meta&gt;</code> element
      (<code><TMPL_VAR NAME="W19_meta" ESCAPE="HTML"></code>). I will use the
      value from the HTTP header
      (<code><TMPL_VAR NAME="W19_use" ESCAPE="HTML"></code>) for this
      validation.
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W20">
  <dt id="W20">Character Encoding mismatch!</dt>
  <dd>
    <p>
      The character encoding specified in the XML declaration
      (<code><TMPL_VAR NAME="W20_xml" ESCAPE="HTML"></code>)
      is different from the value in the <code>&lt;meta&gt;</code> element
      (<code><TMPL_VAR NAME="W20_meta" ESCAPE="HTML"></code>). I will use the
      value from the XML declaration
      (<code><TMPL_VAR NAME="W20_xml" ESCAPE="HTML"></code>) for this
      validation.
    </p>
  </dd>
</TMPL_IF>
<TMPL_IF NAME="W21">
  <dt id="W21">Byte-Order Mark found in UTF-8 File.</dt>
  <dd>
    <p>
      The Unicode Byte-Order Mark (BOM) in UTF-8 encoded files is known to
      cause problems for some text editors and older browsers. You may want
      to consider avoiding its use until it is better supported.
    </p>
  </dd>
</TMPL_IF>

<TMPL_IF NAME="W@@">
  <dt id="W@@"></dt>
  <dd>
    <p>
    </p>
  </dd>
</TMPL_IF>

</dl><!-- End of "warnings". -->
