Extensions Docs Server: Doc conversion script - SVN

chrome/common/extensions/docs/server2/templates/articles/manifest.html

-<div id="pageData-name" class="pageData">Formats: Manifest Files</div>
-<div id="pageData-showTOC" class="pageData">true</div>
+<h1>Formats: Manifest Files</h1>
+
 
 <p>
 Every extension, installable web app, and theme has a
 <a href="http://www.json.org">JSON</a>-formatted manifest file,
 named <code>manifest.json</code>,
 that provides important information.
 </p>
 
 <h2 id="overview"> Field summary </h2>
 
@@ skipping 718 matching lines @@
 
 <p>
 A missing integer is equal to zero.
 For example, 1.1.9.9999 is newer than 1.1.
 </p>
 
 <p>
 For more information, see
 <a href="autoupdate.html">Autoupdating</a>.
 </p>
-<!-- [PENDING: Possibly: point to the store/dashboard and make a big deal of the fact that autoupdating is free if you use them.] -->
+
 
 
 <h3 id="manifest_version">manifest_version</h3>
 
 <p>
 One integer specifying the version of the manifest file format your package
 requires. As of Chrome 18, developers <em>should</em> specify <code>2</code>
 (without quotes) to use the format as described by this document:
 </p>
 
@@ skipping 142 matching lines @@
 <a href="sandboxingEval.html">"Using eval in Chrome Extensions. Safely."</a>
 goes into more detail about implementing a sandboxing workflow that enables use
 of libraries that would otherwise have issues executing under extension's
 <a href="../extensions/contentSecurityPolicy.html">default Content Security
 Policy</a>.
 </p>
 
 <p>
 Sandboxed page may only be specified when using
 <a href="#manifest_version"><code>manifest_version</code></a> 2 or above.
-</p>
+</p>