Add vim modelines to all files.

Signed-off-by: Edward Z. Yang <edwardzyang@thewritingpot.com>

docs/dev-advanced-api.html

@@ -214,3 +214,5 @@ the usual things required are:</p>
 <p>See <code>HTMLPurifier/HTMLModule.php</code> for details.</p>
 
 </body></html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/dev-code-quality.txt

@@ -25,3 +25,5 @@ URIScheme - needs to have callable generic checks
     mailto - doesn't validate emails, doesn't validate querystring
     news - doesn't validate opaque path
     nntp - doesn't constrain path
+
+    vim: et sw=4 sts=4

docs/dev-config-schema.html

@@ -372,3 +372,5 @@ Test.Example</pre>
 
   </body>
 </html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/dev-flush.html

@@ -63,3 +63,5 @@
 </p>
 
 </body></html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/dev-includes.txt

@@ -277,3 +277,5 @@ DEPRECATED-VERSION: If the directive was deprecated, when was it deprecated?
 DEPRECATED-USE: If the directive was deprecated, what should the user use now?
 REQUIRES: What classes does this configuration directive require, but are
     not part of the HTML Purifier core?
+
+    vim: et sw=4 sts=4

docs/dev-naming.html

@@ -78,3 +78,5 @@ help you find the correct functionality more quickly.  Here they are:</p>
 </dl>
 
 </body></html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/dev-optimization.html

@@ -28,3 +28,5 @@ that itch, put it here!</p>
 </ul>
 
 </body></html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/dev-progress.html

@@ -304,3 +304,5 @@ Mozilla on inside and needs -moz-outline, no IE support.</td></tr>
 </table>
 
 </body></html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/enduser-customize.html

@@ -794,3 +794,5 @@ $form->excludes = array('form' => true);</strong></pre>
 </ul>
 
 </body></html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/enduser-id.html

@@ -143,3 +143,5 @@ anchors is beyond me.</p>
 
 </body>
 </html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/enduser-overview.txt

@@ -55,3 +55,5 @@ HTML tags.  Things like blog comments are, in all likelihood, most appropriately
 written in an extremely restrictive set of markup that doesn't require
 all this functionality (or not written in HTML at all), although this may
 be changing in the future with the addition of levels of filtering.
+
+    vim: et sw=4 sts=4

docs/enduser-security.txt

@@ -14,3 +14,5 @@ to be effective. Things to remember:
 
 4. CSS: document pending
 Explain which CSS styles we blocked and why.
+
+    vim: et sw=4 sts=4

docs/enduser-slow.html

@@ -115,3 +115,5 @@ if you decide to do that! Especially if you port HTML Purifier to C++.
 
 </body>
 </html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/enduser-tidy.html

@@ -226,3 +226,5 @@ Other than that, don't worry about it: this all works silently and
 effectively in the background.</p>
 
 </body></html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/enduser-uri-filter.html

@@ -212,3 +212,5 @@ $uri->registerFilter(new HTMLPurifier_URIFilter_<strong>NameOfFilter</strong>())
 </p>
 
 </body></html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/enduser-utf8.html

@@ -1055,3 +1055,5 @@ a more in-depth look into character sets and encodings.</p>
 
 </body>
 </html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/enduser-youtube.html

@@ -148,3 +148,5 @@ with the core!</p>
 
 </body>
 </html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/examples/basic.php

@@ -20,3 +20,4 @@ $pure_html = $purifier->purify($html);
 
 echo '<pre>' . htmlspecialchars($pure_html) . '</pre>';
 
+// vim: et sw=4 sts=4

docs/fixquotes.htc

@@ -4,3 +4,5 @@ function init() {
   element.innerHTML = '“'+element.innerHTML+'”';
 }
 </script>
+
+<!-- vim: et sw=4 sts=4 -->

docs/index.html

@@ -177,3 +177,5 @@ the code. They may be upgraded to HTML files or stay as TXT scratchpads.</p>
 
 </body>
 </html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/proposal-colors.html

@@ -44,3 +44,5 @@ something like that?</li>
 
 </body>
 </html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/proposal-config.txt

@@ -19,3 +19,5 @@ Definition objects are complex datatypes influenced by their respective
 directive namespaces (HTMLDefinition with HTML and CSSDefinition with CSS).
 If any of these directives is updated, HTML Purifier forces the definition
 to be regenerated.
+
+    vim: et sw=4 sts=4

docs/proposal-css-extraction.txt

@@ -30,3 +30,5 @@ Beyond that, HTML Purifier can magically merge common CSS values together,
 and a whole manner of other heuristic things.  HTML Purifier should also
 make it easy for an admin to re-style the HTML semantically. Speed is not
 an issue. Also, better WYSIWYG editors are needed.
+
+    vim: et sw=4 sts=4

docs/proposal-errors.txt

@@ -207,3 +207,5 @@ Don't forget to spruce up output.
 
        - We need a standard CSS to apply (check demo.css for some starting
          styling; some buttons would also be hip)
+
+    vim: et sw=4 sts=4

docs/proposal-filter-levels.txt

@@ -133,3 +133,5 @@ Dramatic - border, list-style-position (list-style), margin, padding,
 
 Dramatic elements substantially change the look of text in ways that should
 probably have been reserved to other areas.
+
+    vim: et sw=4 sts=4

docs/proposal-language.txt

@@ -60,3 +60,5 @@ Neat functionality:
 -  Roman numeral formatting
 
 Items marked with a + likely need to be addressed by HTML Purifier
+
+    vim: et sw=4 sts=4

docs/proposal-new-directives.txt

@@ -41,3 +41,4 @@ implemented, give us a ring, and we'll move it up the priority chain.
     absolute DNS.  While this is actually the preferred method according to
     the RFC, most people opt to use a relative domain name relative to . (root).
 
+    vim: et sw=4 sts=4

docs/ref-content-models.txt

@@ -46,3 +46,5 @@ is eliminated completely, in the latter case, the text of the node
 would is preserved (as the parent node does allow PCDATA).  Custom
 content model implementations probably are not the best way of handling
 these cases, instead, node bubbling should be implemented instead.
+
+    vim: et sw=4 sts=4

docs/ref-css-length.txt

@@ -26,3 +26,5 @@ Watch out: font-sizes can also be nested to get successively larger
 (although I do not relish having to keep track of context font-sizes,
 this may be necessary, especially for some of the more advanced features
 for preventing things like white on white).
+
+    vim: et sw=4 sts=4

docs/ref-devnetwork.html

@@ -42,3 +42,5 @@ the development of this library in these forum threads:</p>
 
 </body>
 </html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/ref-html-modularization.txt

@@ -162,3 +162,5 @@ array of content set names to content set contents. If the content set
 already exists, your values are appended on to it (great for, say,
 registering the font tag as an inline element), otherwise it is
 created. They are substituted into content_model.
+
+    vim: et sw=4 sts=4

docs/ref-proprietary-tags.txt

@@ -22,3 +22,5 @@ HTML Purifier context.
 
 These should be put into their own Tidy module, not loaded by default(?). These
 all qualify as "lenient" transforms.
+
+    vim: et sw=4 sts=4

docs/ref-whatwg.txt

@@ -22,3 +22,5 @@ another DirectLex parser, other parsers like ph5p
 <http://jero.net/lab/ph5p/> can be adapted to DOMLex to support much more
 flexible HTML parsing (a cool feature I've seen is how they resolve
 <b>bold<i>both</b>italic</i>).
+
+    vim: et sw=4 sts=4

docs/specimens/LICENSE

@@ -6,3 +6,5 @@ windows-live-mail-desktop-beta.html - donated by laacz, public domain
 img.png - LGPL, from <http://commons.wikimedia.org/wiki/Image:Pastille_chrome.png>
 
 All other files are by me, and are licensed under LGPL.
+
+    vim: et sw=4 sts=4

docs/specimens/html-align-to-css.html

@@ -162,4 +162,6 @@ div.segment {width:250px; float:left; margin-top:1em;}
 </div>
 
 </body>
-</html>
+</html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/specimens/jochem-blok-word.html

@@ -127,3 +127,5 @@ style='color:black'>www.example.com/disclaimer</span></a><o:p></o:p></span></p>
 </body>
 
 </html>
+
+<!-- vim: et sw=4 sts=4 -->

docs/specimens/windows-live-mail-desktop-beta.html

@@ -71,4 +71,6 @@ style="BORDER-TOP: #dddddd 1px solid; FONT-SIZE: 10pt; MARGIN-BOTTOM: 10px; WIDT
 title="Join Windows Live to share photos using Windows Live Photo E-mail.">Online
 pictures are available for 30 days. <A style="COLOR: #0088e4"
 href="http://g.msn.com/5meen_us/175">Get Windows Live Mail desktop to create
-your own photo e-mails. </A></SPAN></NOBR></DIV></BODY></HTML>
+your own photo e-mails. </A></SPAN></NOBR></DIV></BODY></HTML>
+
+<!-- vim: et sw=4 sts=4 -->

docs/style.css

@@ -72,3 +72,5 @@ q:after {
 .fixme:before {content:"Fix me: "; font-weight:bold; color:#C00; }
 
 #applicability {margin: 1em 5%; font-style:italic;}
+
+/* vim: et sw=4 sts=4 */