- From: Olivier Thereaux <ot@hutz.w3.org>
- Date: Fri, 30 Apr 2004 06:22:31 +0000
- To: www-validator-cvs@w3.org
Update of /sources/public/validator/htdocs/docs
In directory hutz:/tmp/cvs-serv3712
Modified Files:
Tag: validator-0_6_0-branch
users.html
Log Message:
- wrapping the text of option explanations in <p>aragraphs
- updating the doc with a link to the new installation documentation
Index: users.html
===================================================================
RCS file: /sources/public/validator/htdocs/docs/users.html,v
retrieving revision 1.14.2.7
retrieving revision 1.14.2.8
diff -u -d -r1.14.2.7 -r1.14.2.8
--- users.html 25 Sep 2003 19:21:04 -0000 1.14.2.7
+++ users.html 30 Apr 2004 06:22:28 -0000 1.14.2.8
@@ -74,67 +74,71 @@
<dl>
<dt id="option-charset">Encoding</dt>
<dd>
- This allows you to <strong>override</strong> the character encoding
+ <p>This allows you to <strong>override</strong> the character encoding
information about your document. You may use this option for test
purposes, but you will eventually have to serve your document with the
correct character encoding, or the validator will <a href="help#faq-charset">complain</a>
- about it and you document will not be valid.
+ about it and you document will not be valid.</p>
</dd>
<dt id="option-fbc">Use Fallback instead of Override (Encoding) (<code>fbc</code>)</dt>
<dd>
- Uses the <a href="#option-charset">character encoding override</a> mechanism
+ <p>Uses the <a href="#option-charset">character encoding override</a> mechanism
described above, but only does it as a fall back mechanism if the actual document
is not served with character encoding information. Think of this as a gentler
- override mechanism.
+ override mechanism.</p>
</dd>
<dt id="option-doctype">Type</dt>
<dd>
- This allows you to <strong>override</strong> the DOCTYPE declaration for you
+ <p>This allows you to <strong>override</strong> the DOCTYPE declaration for you
document. You may use this option for test
purposes, but you will eventually have to serve your document with the
correct character encoding, or the validator will <a href="help#faq-doctype">complain</a>
- about it and you document will not be valid.
+ about it and you document will not be valid.</p>
</dd>
<dt id="option-fbc">Use Fallback instead of Override (Type) (<code>fbd</code>)</dt>
<dd>
- Uses the <a href="#option-doctype">Doctype override</a> mechanism
+ <p>Uses the <a href="#option-doctype">Doctype override</a> mechanism
described above, but only does it as a fall back mechanism if the actual document
- does not have a Doctype declaration. Think of this as a gentler override mechanism.
+ does not have a Doctype declaration. Think of this as a gentler override mechanism.</p>
</dd>
<dt id="option-ss">Show source input (<code>ss</code>)</dt>
<dd>
- Displays the HTML source of the document you validated and links
+ <p>Displays the HTML source of the document you validated and links
error messages directly to lines in this output. Makes it easy to
- see what's wrong.
+ see what's wrong.</p>
</dd>
<dt id="option-outline">Show an outline of this document (<code>outline</code>)</dt>
<dd>
- Will generate an outline of your document from the H1 - H6 elements.
+ <p>Will generate an outline of your document from the H1 - H6 elements.
For a properly formed document, this will be a nicely nested tree
structure. The visualization of your document's structure makes it
- easier to see where you've skipped a heading.
+ easier to see where you've skipped a heading.</p>
</dd>
<dt id="option-sp">Show parse tree (<code>sp</code>)</dt>
<dd>
- Shows you exactly how the SGML Parser read your document. Probably
+ <p>Shows you exactly how the SGML Parser read your document. Probably
best used only by advanced users as it deals with low-level SGML
- constructs.
+ constructs.</p>
</dd>
<dt id="option-noatt">exclude attributes from the parse tree (<code>noatt</code>)</dt>
- <dd>Suppress attributes from the <a href="#option-sp">parse tree</a> to make it
- more readable.</dd>
+ <dd>
+ <p>Suppress attributes from the <a href="#option-sp">parse tree</a> to make it
+ more readable.</p>
+ </dd>
<dt id="option-no200">Validate error pages</dt>
- <dd>The Markup Validator will usually tell you if the page you tried to validate
- could not be retrieved (for example, if the server gave a "404 not found" message.
- In some circumstances you may want to be able to validate the error page sent by
- the server. This is the option to use then.
+ <dd>
+ <p>The Markup Validator will usually tell you if the page you tried to validate
+ could not be retrieved (for example, if the server gave a "404 not found" message.
+ In some circumstances you may want to be able to validate the error page sent by
+ the server. This is the option to use then.</p>
</dd>
<dt id="option-verbose">Verbose Output</dt>
- <dd>This option triggers verbose output. By default the validator will only output
- the validity result if the document is valid, but you may want to have the rest of
- the information (outline, etc.). This is the option to use then.
+ <dd>
+ <p>This option triggers verbose output. By default the validator will only output
+ the validity result if the document is valid, but you may want to have the rest of
+ the information (outline, etc.). This is the option to use then.</p>
</dd>
@@ -430,13 +434,16 @@
<div id="Installing" class="stb">
<h3>Installing a local Validator</h3>
<p>
- You can download the Validator to run on your own system, but it's not
- recommended for average users as the process is rather complex and
- involves obscure incantations on the command line. <tt>:-)</tt>
+ You can download the Validator to run on your own system. For Web design departments
+ or agencies it can be a very good idea, saving time and allowing you to not send
+ documents under work or confidential pages over the wire, but it is a complex operation,
+ and is not recommended for average users, for which the free online service at W3C
+ should suffice.
</p>
<p>
- If you feel you're up to the task, you can find the information you need
- in our <a href="devel.html">Developer Manual</a>.
+ We have created a simple <a href="install.html">Installation manual</a>, which, along with
+ the <a href="devel.html">Developer's information</a>, should help you install a local instance
+ of the Markup Validator in your own network easily.
</p>
</div>
</div>
Received on Friday, 30 April 2004 02:22:32 UTC