validator/share/templates/en_US jumpbar.tmpl,1.11,1.12 warnings.tmpl,1.45,1.46

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

Modified Files:
	jumpbar.tmpl warnings.tmpl 
Log Message:
Adding W27 (suggest adding charset info within document) and W28 (explanation of UTF-8 force in direct input mode),
plus softening the wording of the preparse warning-info section of validation results.

Index: warnings.tmpl
RCS file: /sources/public/validator/share/templates/en_US/warnings.tmpl,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -d -r1.45 -r1.46
--- warnings.tmpl	14 Nov 2008 16:22:52 -0000	1.45
+++ warnings.tmpl	28 Jan 2009 15:30:17 -0000	1.46
@@ -1,5 +1,5 @@
-<h3 id="preparse_warnings">Potential Issues</h3>
-<p>The following missing or conflicting information caused the validator to perform guesswork prior to validation. If the guess or fallback is incorrect, it may make validation results entirely incoherent. It is <em>highly recommended</em> 
+<h3 id="preparse_warnings">Notes and Potential Issues</h3>
+<p>The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is <em>highly recommended</em> 
 to check these potential issues, and, if necessary, fix them and re-validate the document.</p>
 <ol id="warnings">
@@ -514,6 +514,22 @@
+  <li class="msg_info" id="W27"><p><span class="err_type"><img src="images/info_icons/info.png" alt="Info" title="Info" /></span> <span class="msg">No Character encoding declared at document level</span></p>
+    <p>No character encoding information was found within the document, either in an HTML <code>meta</code> element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.</p>
+    <p>See <a href="">this tutorial on character encoding</a> for techniques and explanations.</p>
+  </li>
+  <li class="msg_info" id="W28"><p><span class="err_type"><img src="images/info_icons/info.png" alt="Info" title="Info" /></span> <span class="msg">Using Direct Input mode: UTF-8 character encoding assumed</span></p>
+    <p>Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator's form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.</p>
+    <p>If you notice a discrepancy in detected character encoding between the the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.</p>
+  </li>

Index: jumpbar.tmpl
RCS file: /sources/public/validator/share/templates/en_US/jumpbar.tmpl,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- jumpbar.tmpl	2 Oct 2007 02:44:08 -0000	1.11
+++ jumpbar.tmpl	28 Jan 2009 15:30:17 -0000	1.12
@@ -3,7 +3,7 @@
         <ul class="navbar" id="jumpbar">
                 <li><strong>Jump To:</strong></li>
                 <TMPL_IF NAME="have_warnings">
-                        <li><a href="#preparse_warnings">Potential Issues</a></li>
+                        <li><a href="#preparse_warnings">Notes and Potential Issues</a></li>
                 <TMPL_IF NAME="has_errors">
           <li><a title="Result of Validation" href="#result">Validation Output</a></li>

Received on Wednesday, 28 January 2009 15:36:38 UTC