validator/share/templates/en_US warnings.tmpl,1.16,1.17

Update of /sources/public/validator/share/templates/en_US
In directory hutz:/tmp/cvs-serv31700

Modified Files:
	warnings.tmpl 
Log Message:
making preparse warning a list, not a DL (abusive)

Index: warnings.tmpl
===================================================================
RCS file: /sources/public/validator/share/templates/en_US/warnings.tmpl,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- warnings.tmpl	24 Jul 2006 07:06:48 -0000	1.16
+++ warnings.tmpl	20 Feb 2007 02:07:58 -0000	1.17
@@ -1,9 +1,11 @@
-<dl id="warnings">
+<h3 id="preparse_warnings">Important Warnings</h3>
+<p>The validator has found the following problem(s) prior to validation, 
+        which should be addressed in priority:</p>
+<ul 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>
+  <li class="msg_warn" id="W01"><span class="msg">Missing "<code>charset</code>" attribute for
+    "<code><TMPL_VAR NAME="W01_ct" ESCAPE="HTML"></code>" document.</span>
     <p>
       The HTTP <code>Content-Type</code> header
       (<code><TMPL_VAR NAME="W01_ct" ESCAPE="HTML"></code>) sent by your web
@@ -23,39 +25,39 @@
       your <TMPL_IF NAME="W01_upload">browser<TMPL_ELSE>server</TMPL_IF> send
       this new encoding information.
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W02">
-  <dt id="W02">No Character Encoding Found!</dt>
-  <dd>
+  <li class="msg_warn" id="W02"><span class="msg">No Character Encoding Found!</span>
+  
     <p>
       Falling back to
       "<code><TMPL_VAR NAME="W02_charset" ESCAPE="HTML"></code>"
       (<a href="docs/users.html#fbc">explain...</a>).
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W03">
-  <dt id="W03">Character Encoding Override in effect!</dt>
-  <dd>
+  <li class="msg_warn" id="W03"><span class="msg">Character Encoding Override in effect!</span>
+  
     <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>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W04">
-  <dt id="W04">No Character Encoding Found!
+  <li class="msg_warn" id="W04"><span class="msg">No Character Encoding Found!</span>
     <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 
@@ -113,26 +115,26 @@
     <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>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W05">
-  <dt id="W05"><code>DOCTYPE</code> Override in effect!</dt>
-  <dd>
+  <li class="msg_warn" id="W05"><span class="msg"><code>DOCTYPE</code> Override in effect!</span>
+  
     <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>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W06">
-  <dt id="W06">Unable to Determine Parse Mode!</dt>
-  <dd><p>Falling back to SGML mode.</p></dd>
+  <li class="msg_warn" id="W06"><span class="msg">Unable to Determine Parse Mode!</span>
+  <p>Falling back to SGML mode.</p></li>
 </TMPL_IF>
 <TMPL_IF NAME="W07">
-  <dt id="W07">Contradictory Parse Modes Detected!</dt>
-  <dd>
+  <li class="msg_warn" id="W07"><span class="msg">Contradictory Parse Modes Detected!</span>
+  
     <p>
       The MIME Media Type
       (<code><TMPL_VAR NAME="W07_mime" ESCAPE="HTML"></code>) indicated parse
@@ -142,11 +144,11 @@
        <TMPL_VAR NAME="W07_ct" ESCAPE="HTML"> mode based on the
        <code>Content-Type</code> header.
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W08">
-  <dt id="W08">Unknown Parse Mode!</dt>
-  <dd>
+  <li class="msg_warn" id="W08"><span class="msg">Unknown Parse Mode!</span>
+  
     <p>
       The MIME Media Type
       (<code><TMPL_VAR NAME="W08_mime" ESCAPE="HTML"></code>) for this
@@ -155,11 +157,11 @@
       based on the <code>DOCTYPE</code> Declaration in your document. Parsing
       will continue in SGML mode.
     </p>
-  </dd>
+  </li>
 </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>
+  <li class="msg_warn" id="W09"><span class="msg">No <code>DOCTYPE</code> found! Attempting validation with <TMPL_VAR NAME="W09_dtd" ESCAPE="HTML">.</span>
+  
     <p>
       The DOCTYPE Declaration was not recognized or is missing. This
       probably means that the Formal Public Identifier contains a spelling
@@ -207,37 +209,37 @@
     from our <acronym title="Frequently Asked Questions">FAQ</acronym>.</p>
   </TMPL_IF>
 
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W10">
-  <dt id="W10">Unknown Namespace Found</dt>
-  <dd>
+  <li class="msg_warn" id="W10"><span class="msg">Unknown Namespace Found</span>
+  
     <p>
       Unknown namespace "<code><TMPL_VAR NAME="W10_ns" ESCAPE="HTML"></code>"
       for <TMPL_VAR NAME="W10_type" ESCAPE="HTML"> document!
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W11">
-  <dt id="W11">Namespace Found in non-XML Document</dt>
-  <dd>
+  <li class="msg_warn" id="W11"><span class="msg">Namespace Found in non-XML Document</span>
+  
     <p>
       Namespace "<code><TMPL_VAR NAME="W11_rns" ESCAPE="HTML"></code>" found,
       but document type is not XML!
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W12">
-  <dt id="W12">No Namespace Found</dt>
-  <dd>
+  <li class="msg_warn" id="W12"><span class="msg">No Namespace Found</span>
+  
     <p>
       No Namespace was found, but document type requires one to be present!
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W13">
-  <dt id="W13"><code>DOCTYPE</code> Override in effect!</dt>
-  <dd>
+  <li class="msg_warn" id="W13"><span class="msg"><code>DOCTYPE</code> Override in effect!</span>
+  
     <p>
       The detected DOCTYPE Declaration
       "<code><TMPL_VAR NAME="W13_org"></code>" has been
@@ -246,32 +248,32 @@
       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>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W14">
-  <dt id="W14">No <code>DOCTYPE</code> Found!</dt>
-  <dd>
+  <li class="msg_warn" id="W14"><span class="msg">No <code>DOCTYPE</code> Found!</span>
+  
     <p>
       Falling back to HTML 4.01 Transitional.
       (<a href="docs/users.html#fbd">explain...</a>)
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W15">
-  <dt id="W15"><code>DOCTYPE</code> Override in effect!</dt>
-  <dd>
+  <li class="msg_warn" id="W15"><span class="msg"><code>DOCTYPE</code> Override in effect!</span>
+  
     <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>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W16">
-  <dt id="W16">No DOCTYPE Found! Falling Back to
-    <TMPL_VAR NAME="W16_dtd" ESCAPE="HTML">.</dt>
-  <dd>
+  <li class="msg_warn" id="W16"><span class="msg">No DOCTYPE Found! Falling Back to
+    <TMPL_VAR NAME="W16_dtd" ESCAPE="HTML">.</span>
+  
     <p>
       A DOCTYPE Declaration is mandatory for most current markup languages
       and without one it is impossible to reliably validate this document.
@@ -295,22 +297,22 @@
       <a href="docs/help.html#faq-doctype">Tell me more...</a>
     </p>
   </TMPL_IF>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W17">
-  <dt id="W17">No Character Encoding detected!</dt>
-  <dd>
+  <li class="msg_warn" id="W17"><span class="msg">No Character Encoding detected!</span>
+  
     <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>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W18">
-  <dt id="W18">Character Encoding mismatch!</dt>
-  <dd>
+  <li class="msg_warn" id="W18"><span class="msg">Character Encoding mismatch!</span>
+  
     <p>
       The character encoding specified in the HTTP header
         (<code><TMPL_VAR NAME="W18_http" ESCAPE="HTML"></code>)
@@ -319,11 +321,11 @@
       I will use the value from the HTTP header
         (<code><TMPL_VAR NAME="W18_use" ESCAPE="HTML"></code>).
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W19">
-  <dt id="W19">Character Encoding mismatch!</dt>
-  <dd>
+  <li class="msg_warn" id="W19"><span class="msg">Character Encoding mismatch!</span>
+  
     <p>
       The character encoding specified in the HTTP header
         (<code><TMPL_VAR NAME="W19_http" ESCAPE="HTML"></code>)
@@ -333,11 +335,11 @@
       (<code><TMPL_VAR NAME="W19_use" ESCAPE="HTML"></code>) for this
       validation.
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W20">
-  <dt id="W20">Character Encoding mismatch!</dt>
-  <dd>
+  <li class="msg_warn" id="W20"><span class="msg">Character Encoding mismatch!</span>
+  
     <p>
       The character encoding specified in the XML declaration
       (<code><TMPL_VAR NAME="W20_xml" ESCAPE="HTML"></code>)
@@ -347,25 +349,34 @@
       (<code><TMPL_VAR NAME="W20_xml" ESCAPE="HTML"></code>) for this
       validation.
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 <TMPL_IF NAME="W21">
-  <dt id="W21">Byte-Order Mark found in UTF-8 File.</dt>
-  <dd>
+  <li class="msg_warn" id="W21"><span class="msg">Byte-Order Mark found in UTF-8 File.</span>
+  
     <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>
+  </li>
+</TMPL_IF>
+
+<TMPL_IF NAME="W22">
+  <li class="msg_warn" id="W22"><span class="msg">XML not well-formed</span>
+  
+    <p><TMPL_VAR NAME="W22_Messages" ESCAPE="HTML">
+    </p>
+  </li>
 </TMPL_IF>
 
+
 <TMPL_IF NAME="W@@">
-  <dt id="W@@"></dt>
-  <dd>
+  <li class="msg_warn" id="W@@">
+  
     <p>
     </p>
-  </dd>
+  </li>
 </TMPL_IF>
 
-</dl><!-- End of "warnings". -->
+</ul><!-- End of "warnings". -->

Received on Tuesday, 20 February 2007 02:08:09 UTC