hixie: <meta> examples. (whatwg r3789)

hixie: <meta> examples. (whatwg r3789)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2958&r2=1.2959&f=h
http://html5.org/tools/web-apps-tracker?from=3788&to=3789

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2958
retrieving revision 1.2959
diff -u -d -r1.2958 -r1.2959
--- Overview.html 10 Sep 2009 09:07:21 -0000 1.2958
+++ Overview.html 10 Sep 2009 09:15:57 -0000 1.2959
@@ -9580,9 +9580,23 @@
 
    <dt><dfn id="meta-generator" title="meta-generator">generator</dfn></dt>
 
-   <dd><p>The value must be a free-form string that identifies the
-   software used to generate the document. This value must not be used
-   on hand-authored pages.</dd>
+   <dd>
+
+    <p>The value must be a free-form string that identifies the
+    software used to generate the document. This value must not be
+    used on hand-authored pages.</p>
+
+    <div class="example">
+
+     <p>Here is what a tool called "Frontweaver" could include in its
+     output, in the page's <code><a href="#the-head-element-0">head</a></code> element, to identify
+     itself as the tool used to generate the page:</p>
+
+     <pre>&lt;meta name=generator content="Frontweaver 8.2"&gt;</pre>
+
+    </div>
+
+   </dd>
 
   </dl><h5 id="other-metadata-names"><span class="secno">4.2.5.2 </span>Other metadata names</h5><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/27">ISSUE-27</a> (rel-ownership) blocks progress to Last Call</span><p><dfn id="concept-meta-extensions" title="concept-meta-extensions">Extensions to the predefined
   set of metadata names</dfn> may be registered in the <a href="http://wiki.whatwg.org/wiki/MetaExtensions">WHATWG Wiki
@@ -9996,6 +10010,17 @@
     represents a number of seconds before the page is to be replaced
     by the page at the given <a href="#url">URL</a>.</p>
 
+    <div class="example">
+
+     <p>A news organisation's front page could include the following
+     markup in the page's <code><a href="#the-head-element-0">head</a></code> element, to ensure that
+     the page automatically reloads from the server every five
+     minutes:</p>
+
+     <pre>&lt;meta http-equiv="Refresh" content="600"&gt;</pre>
+
+    </div>
+
    </dd>
 
   </dl><p>There must not be more than one <code><a href="#meta">meta</a></code> element with
@@ -10105,7 +10130,20 @@
   </div><p class="note">Using non-UTF-8 encodings can have unexpected
   results on form submission and URL encodings, which use the
   <a href="#document-s-character-encoding">document's character encoding</a> by default.<p>In XHTML, the XML declaration should be used for inline character
-  encoding information, if necessary.<h4 id="the-style-element"><span class="secno">4.2.6 </span>The <dfn><code>style</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Working draft</i><dl class="element"><dt>Categories</dt>
+  encoding information, if necessary.<div class="example">
+
+   <p>In HTML, to declare that the character encoding is UTF-8, the
+   author could include the following markup near the top of the
+   document (in the <code><a href="#the-head-element-0">head</a></code> element):</p>
+
+   <pre>&lt;meta charset="utf-8"&gt;</pre>
+
+   <p>In XML, the XML declaration would be used instead, at the very
+   top of the markup:</p>
+
+   <pre>&lt;?xml version="1.0" encoding="utf-8"?&gt;</pre>
+
+  </div><h4 id="the-style-element"><span class="secno">4.2.6 </span>The <dfn><code>style</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Working draft</i><dl class="element"><dt>Categories</dt>
    <dd><a href="#metadata-content">Metadata content</a>.</dd>
    <dd>If the <code title="attr-style-scoped"><a href="#attr-style-scoped">scoped</a></code> attribute is present: <a href="#flow-content">flow content</a>.</dd>
    <dt>Contexts in which this element may be used:</dt>

Received on Thursday, 10 September 2009 09:17:02 UTC