Add vim modelines to all files.

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

library/HTMLPurifier/ConfigSchema/schema/Attr.AllowedFrameTargets.txt

@@ -9,3 +9,4 @@ W3C's recommendation. XHTML 1.0 Strict does not permit the target attribute
 so this directive will have no effect in that doctype. XHTML 1.1 does not
 enable the Target module by default, you will have to manually enable it
 (see the module documentation for more details.)
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.AllowedRel.txt

@@ -6,3 +6,4 @@ DEFAULT: array()
 List of allowed forward document relationships in the rel attribute. Common
 values may be nofollow or print. By default, this is empty, meaning that no
 document relationships are allowed.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.AllowedRev.txt

@@ -6,3 +6,4 @@ DEFAULT: array()
 List of allowed reverse document relationships in the rev attribute. This
 attribute is a bit of an edge-case; if you don't know what it is for, stay
 away.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.DefaultImageAlt.txt

@@ -8,3 +8,4 @@ previously specified an alt attribute.  This applies to all images without
 a valid alt attribute, as opposed to %Attr.DefaultInvalidImageAlt, which
 only applies to invalid images, and overrides in the case of an invalid image.
 Default behavior with null is to use the basename of the src tag for the alt.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.DefaultInvalidImage.txt

@@ -6,3 +6,4 @@ This is the default image an img tag will be pointed to if it does not have
 a valid src attribute.  In future versions, we may allow the image tag to
 be removed completely, but due to design issues, this is not possible right
 now.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.DefaultInvalidImageAlt.txt

@@ -5,3 +5,4 @@ DEFAULT: 'Invalid image'
 This is the content of the alt tag of an invalid image if the user had not
 previously specified an alt attribute.  It has no effect when the image is
 valid but there was no alt attribute present.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.DefaultTextDir.txt

@@ -7,3 +7,4 @@ parsed.  This generally is the same as the value of the dir attribute in
 HTML, or ltr if that is not specified.
 --ALLOWED--
 'ltr', 'rtl'
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.EnableID.txt

@@ -13,3 +13,4 @@ you use (%Attr.IDBlacklist) or prefixing all user supplied IDs
 pre-1.2.0 versions.
 --ALIASES--
 HTML.EnableAttrID
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.IDBlacklist.txt

@@ -2,3 +2,4 @@ Attr.IDBlacklist
 TYPE: list
 DEFAULT: array()
 DESCRIPTION: Array of IDs not allowed in the document.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.IDBlacklistRegexp.txt

@@ -6,3 +6,4 @@ DEFAULT: NULL
 PCRE regular expression to be matched against all IDs. If the expression is
 matches, the ID is rejected. Use this with care: may cause significant
 degradation. ID matching is done after all other validation.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.IDPrefix.txt

@@ -9,3 +9,4 @@ that they are still usable, but will not conflict with core page IDs.
 Example: setting the directive to 'user_' will result in a user submitted
 'foo' to become 'user_foo'  Be sure to set %HTML.EnableAttrID to true
 before using this.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.IDPrefixLocal.txt

@@ -11,3 +11,4 @@ clobber each other. Ideal values are unique identifiers for the content it
 represents (i.e. the id of the row in the database). Be sure to add a
 seperator (like an underscore) at the end.  Warning: this directive will
 not work unless %Attr.IDPrefix is set to a non-empty value!
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Attr.txt

@@ -1,2 +1,3 @@
 Attr
 DESCRIPTION: Features regarding attribute validation.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/AutoFormat.AutoParagraph.txt

@@ -28,3 +28,4 @@ DEFAULT: false
   in <code>div</code> tags (the behavior is slightly different outside of
   the root node.)
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/AutoFormat.Custom.txt

@@ -9,4 +9,4 @@ DEFAULT: array()
   Specify an array of injector names (class name minus the prefix)
   or concrete implementations. Injector class must exist.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/AutoFormat.DisplayLinkURI.txt

@@ -8,3 +8,4 @@ DEFAULT: false
   those links. For example, <a href="http://example.com">example</a> becomes
   example (<a>http://example.com</a>).
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/AutoFormat.Linkify.txt

@@ -9,4 +9,4 @@ DEFAULT: false
   https URLs. <code>a</code> tags with the <code>href</code> attribute
   must be allowed.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/AutoFormat.PurifierLinkify.txt

@@ -9,4 +9,4 @@ DEFAULT: false
   syntax <a>%Namespace.Directive</a> to links. <code>a</code> tags
   with the <code>href</code> attribute must be allowed.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/AutoFormat.RemoveEmpty.txt

@@ -42,3 +42,4 @@ DEFAULT: false
   if a tag looked empty on the way end, it will get removed; if HTML Purifier
   made it empty, it will stay.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/AutoFormat.txt

@@ -1,2 +1,3 @@
 AutoFormat
 DESCRIPTION: Configuration for activating auto-formatting functionality (also known as <code>Injector</code>s)
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/AutoFormatParam.PurifierLinkifyDocURL.txt

@@ -9,4 +9,4 @@ DEFAULT: '#%s'
   into the configuration's namespace and directive names sans the percent
   sign.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/AutoFormatParam.txt

@@ -1,2 +1,3 @@
 AutoFormatParam
 DESCRIPTION: Configuration for customizing auto-formatting functionality
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/CSS.AllowImportant.txt

@@ -5,3 +5,4 @@ VERSION: 3.1.0
 --DESCRIPTION--
 This parameter determines whether or not !important cascade modifiers should
 be allowed in user CSS. If false, !important will stripped.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/CSS.AllowTricky.txt

@@ -8,3 +8,4 @@ values. Tricky CSS properties/values can drastically modify page layout or
 be used for deceptive practices but do not directly constitute a security risk.
 For example, <code>display:none;</code> is considered a tricky property that
 will only be allowed if this directive is set to true.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/CSS.AllowedProperties.txt

@@ -15,3 +15,4 @@ DEFAULT: NULL
     <strong>Warning:</strong> If another directive conflicts with the
     elements here, <em>that</em> directive will win and override.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/CSS.DefinitionRev.txt

@@ -8,4 +8,4 @@ DEFAULT: 1
     Revision identifier for your custom definition. See
     %HTML.DefinitionRev for details.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/CSS.MaxImgLength.txt

@@ -13,3 +13,4 @@ VERSION: 3.1.1
  subtle differences in the input format (the CSS max is a number with
  a unit).
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/CSS.Proprietary.txt

@@ -7,4 +7,4 @@ DEFAULT: false
 <p>
     Whether or not to allow safe, proprietary CSS values.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/CSS.txt

@@ -1,2 +1,3 @@
 CSS
 DESCRIPTION: Configuration regarding allowed CSS.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Cache.DefinitionImpl.txt

@@ -11,3 +11,4 @@ performance degradation).
 
 --ALIASES--
 Core.DefinitionCache
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Cache.SerializerPath.txt

@@ -10,4 +10,4 @@ DEFAULT: NULL
     HTML Purifier library inside DefinitionCache/Serializer. This
     path must be writable by the webserver.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Cache.txt

@@ -1,2 +1,3 @@
 Cache
 DESCRIPTION: Configuration for DefinitionCache and related subclasses.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.AggressivelyFixLt.txt

@@ -14,4 +14,5 @@ DEFAULT: true
 <p>
     <strong>Notice:</strong> This directive's default turned from false to true
     in HTML Purifier 3.2.0.
-</p>
+</p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.CollectErrors.txt

@@ -9,3 +9,4 @@ is a useful way to give feedback to your users. <strong>Warning:</strong>
 Currently this feature is very patchy and experimental, with lots of
 possible error messages not yet implemented. It will not cause any
 problems, but it may not help your users either.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.ColorKeywords.txt

@@ -25,5 +25,4 @@ array (
 
 Lookup array of color names to six digit hexadecimal number corresponding
 to color, with preceding hash mark. Used when parsing colors.
-
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.ConvertDocumentToFragment.txt

@@ -11,3 +11,4 @@ processing is not necessary.
 
 --ALIASES--
 Core.AcceptFullDocuments
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.DirectLexLineNumberSyncInterval.txt

@@ -14,4 +14,4 @@ DEFAULT: 0
   This has no effect when %Core.MaintainLineNumbers is disabled or DirectLex is
   not being used.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.Encoding.txt

@@ -12,3 +12,4 @@ entities), making it pretty useless for anything except the most I18N-blind
 applications, although %Core.EscapeNonASCIICharacters offers fixes this
 trouble with another tradeoff. This directive only accepts ISO-8859-1 if
 iconv is not enabled.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.EscapeInvalidChildren.txt

@@ -7,3 +7,4 @@ parent element will be transformed into text as if it were ASCII. When
 false, that element and all internal tags will be dropped, though text will
 be preserved.  There is no option for dropping the element but preserving
 child nodes.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.EscapeInvalidTags.txt

@@ -4,3 +4,4 @@ DEFAULT: false
 --DESCRIPTION--
 When true, invalid tags will be written back to the document as plain text.
 Otherwise, they are silently dropped.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.EscapeNonASCIICharacters.txt

@@ -10,3 +10,4 @@ can be expressed in the non-UTF-8 encoding will be entity-ized, which can
 be a real downer for encodings like Big5. It also assumes that the ASCII
 repetoire is available, although this is the case for almost all encodings.
 Anyway, use UTF-8!
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.HiddenElements.txt

@@ -16,4 +16,4 @@ array (
   tag, which defines some presentational changes but does not hide its
   contents.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.Language.txt

@@ -7,5 +7,4 @@ DEFAULT: 'en'
 ISO 639 language code for localizable things in HTML Purifier to use,
 which is mainly error reporting. There is currently only an English (en)
 translation, so this directive is currently useless.
-
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.LexerImpl.txt

@@ -31,3 +31,4 @@ implementation)
     to use it.
   </dd>
 </dl>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.MaintainLineNumbers.txt

@@ -13,4 +13,4 @@ DEFAULT: NULL
   If the value is null, an appropriate value will be selected based
   on other configuration.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.RemoveInvalidImg.txt

@@ -9,4 +9,4 @@ VERSION: 1.3.0
   tags, as the attribute validation strategy is not authorized to
   remove elements from the document. Revert to pre-1.3.0 behavior by setting to false.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.RemoveScriptContents.txt

@@ -9,3 +9,4 @@ DEPRECATED-USE: Core.HiddenElements
   This directive enables HTML Purifier to remove not only script tags
   but all of their contents.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Core.txt

@@ -1,2 +1,3 @@
 Core
 DESCRIPTION: Core features that are always available.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Filter.Custom.txt

@@ -8,3 +8,4 @@ DEFAULT: array()
   equivalent of the now deprecated <code>HTMLPurifier-&gt;addFilter()</code>
   method. Specify an array of concrete implementations.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Filter.ExtractStyleBlocks.txt

@@ -71,3 +71,4 @@ EXTERNAL: CSSTidy
   height (somewhat reasonable). Whether or not these measures should be
   used is left to the reader.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Filter.YouTube.txt

@@ -8,3 +8,4 @@ DEFAULT: false
   <a href="http://htmlpurifier.org/docs/enduser-youtube.html">this document
   on embedding videos</a> for more information on what this filter does.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Filter.txt

@@ -1,2 +1,3 @@
 Filter
 DESCRIPTION: Directives for turning filters on and off, or specifying custom filters.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/FilterParam.ExtractStyleBlocksEscaping.txt

@@ -11,4 +11,4 @@ ALIASES: Filter.ExtractStyleBlocksEscaping
   if the contents of StyleBlocks will be placed in an external stylesheet,
   where there is no risk of it being interpreted as HTML.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/FilterParam.ExtractStyleBlocksScope.txt

@@ -26,3 +26,4 @@ ALIASES: Filter.ExtractStyleBlocksScope
   Purifier, and I am working to get it fixed. Until then, HTML Purifier
   performs a basic check to prevent this.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/FilterParam.ExtractStyleBlocksTidyImpl.txt

@@ -12,3 +12,4 @@ DEFAULT: NULL
   disable cleaning. In addition, you can supply your own concrete implementation
   of Tidy's interface to use, although I don't know why you'd want to do that.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/FilterParam.txt

@@ -1,2 +1,3 @@
 FilterParam
 DESCRIPTION: Configuration for filters.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.Allowed.txt

@@ -19,4 +19,4 @@ DEFAULT: NULL
     broken whitelists. If %HTML.AllowedElements or %HTML.AllowedAttributes
     are set, this directive has no effect.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.AllowedAttributes.txt

@@ -16,4 +16,4 @@ DEFAULT: NULL
     directive.  You must set that directive to true before you can use
     IDs at all.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.AllowedElements.txt

@@ -15,4 +15,4 @@ DEFAULT: NULL
     <strong>Warning:</strong> If another directive conflicts with the
     elements here, <em>that</em> directive will win and override.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.AllowedModules.txt

@@ -17,4 +17,4 @@ DEFAULT: NULL
     by this directive. Modules defined in %HTML.CoreModules are not
     affected by this directive.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.BlockWrapper.txt

@@ -15,4 +15,4 @@ DEFAULT: 'p'
     The <code>&lt;p&gt;</code> tags can be replaced with whatever you desire,
     as long as it is a block level element.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.CoreModules.txt

@@ -20,4 +20,4 @@ array (
     are used. You can set this to a blank array to disable core module
     protection, but this is not recommended.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.CustomDoctype.txt

@@ -6,5 +6,4 @@ DEFAULT: NULL
 
 A custom doctype for power-users who defined there own document
 type. This directive only applies when %HTML.Doctype is blank.
-
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.DefinitionID.txt

@@ -30,4 +30,4 @@ $def->addAttribute('a', 'tabindex', 'Number');
     You <em>must</em> specify a value to this directive to use the
     advanced API features.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.DefinitionRev.txt

@@ -13,4 +13,4 @@ DEFAULT: 1
     up any older revisions of your definition as well as flush the
     cache.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.Doctype.txt

@@ -8,3 +8,4 @@ this name for sake of simplicity. When non-blank, this will override any
 older directives like %HTML.XHTML or %HTML.Strict.
 --ALLOWED--
 'HTML 4.01 Transitional', 'HTML 4.01 Strict', 'XHTML 1.0 Transitional', 'XHTML 1.0 Strict', 'XHTML 1.1'
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.ForbiddenAttributes.txt

@@ -18,3 +18,4 @@ DEFAULT: array()
     out that directive for a discussion of why you
     should think twice before using this directive.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.ForbiddenElements.txt

@@ -17,3 +17,4 @@ DEFAULT: array()
     a nasty surprise when people start using the <code>background-image</code>
     CSS property.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.MaxImgLength.txt

@@ -10,4 +10,5 @@ VERSION: 3.1.1
  This directive is similar to %CSS.MaxImgLength, and both should be
  concurrently edited, although there are
  subtle differences in the input format (the HTML max is an integer).
-</p>
+</p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.Parent.txt

@@ -9,4 +9,4 @@ DEFAULT: 'div'
     inserted in.  An interesting variation would be using span as the
     parent element, meaning that only inline tags would be allowed.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.Proprietary.txt

@@ -9,3 +9,4 @@ DEFAULT: false
     <strong>Warning:</strong> This can cause your documents to stop
     validating!
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.SafeEmbed.txt

@@ -10,4 +10,5 @@ DEFAULT: false
     element and will cause your website to stop validating. You probably want
     to enable this with %HTML.SafeObject.
     <strong>Highly experimental.</strong>
-</p>
+</p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.SafeObject.txt

@@ -11,3 +11,4 @@ DEFAULT: false
     although embed tags will cause your website to stop validating.
     <strong>Highly experimental.</strong>
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.Strict.txt

@@ -6,3 +6,4 @@ DEPRECATED-VERSION: 1.7.0
 DEPRECATED-USE: HTML.Doctype
 --DESCRIPTION--
 Determines whether or not to use Transitional (loose) or Strict rulesets.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.TidyAdd.txt

@@ -5,4 +5,4 @@ DEFAULT: array()
 --DESCRIPTION--
 
 Fixes to add to the default set of Tidy fixes as per your level.
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.TidyLevel.txt

@@ -21,3 +21,4 @@ There are four allowed values:</p>
 
 --ALLOWED--
 'none', 'light', 'medium', 'heavy'
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.TidyRemove.txt

@@ -5,4 +5,4 @@ DEFAULT: array()
 --DESCRIPTION--
 
 Fixes to remove from the default set of Tidy fixes as per your level.
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.Trusted.txt

@@ -5,3 +5,4 @@ DEFAULT: false
 --DESCRIPTION--
 Indicates whether or not the user input is trusted or not. If the input is
 trusted, a more expansive set of allowed tags and attributes will be used.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.XHTML.txt

@@ -8,3 +8,4 @@ DEPRECATED-USE: HTML.Doctype
 Determines whether or not output is XHTML 1.0 or HTML 4.01 flavor.
 --ALIASES--
 Core.XHTML
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/HTML.txt

@@ -1,2 +1,3 @@
 HTML
 DESCRIPTION: Configuration regarding allowed HTML.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Output.CommentScriptContents.txt

@@ -7,3 +7,4 @@ Determines whether or not HTML Purifier should attempt to fix up the
 contents of script tags for legacy browsers with comments.
 --ALIASES--
 Core.CommentScriptContents
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Output.Newline.txt

@@ -10,4 +10,4 @@ DEFAULT: NULL
     you can manually override it here. Remember, \r\n is Windows, \r
     is Mac, and \n is Unix.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Output.SortAttr.txt

@@ -11,3 +11,4 @@ DEFAULT: false
   to text diffs. If you're not seeing this bug, chances are, you don't need
   this directive.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Output.TidyFormat.txt

@@ -22,3 +22,4 @@ DEFAULT: false
 </p>
 --ALIASES--
 Core.TidyFormat
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Output.txt

@@ -1,2 +1,3 @@
 Output
 DESCRIPTION: Configuration relating to the generation of (X)HTML.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Test.ForceNoIconv.txt

@@ -4,3 +4,4 @@ DEFAULT: false
 --DESCRIPTION--
 When set to true, HTMLPurifier_Encoder will act as if iconv does not exist
 and use only pure PHP implementations.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/Test.txt

@@ -1,2 +1,3 @@
 Test
 DESCRIPTION: Developer testing configuration for our unit tests.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.AllowedSchemes.txt

@@ -12,3 +12,4 @@ array (
 --DESCRIPTION--
 Whitelist that defines the schemes that a URI is allowed to have.  This
 prevents XSS attacks from using pseudo-schemes like javascript or mocha.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.Base.txt

@@ -14,4 +14,4 @@ DEFAULT: NULL
     <strong>Warning:</strong> If set, the scheme on this URI
     overrides the one specified by %URI.DefaultScheme.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.DefaultScheme.txt

@@ -7,4 +7,4 @@ DEFAULT: 'http'
     Defines through what scheme the output will be served, in order to
     select the proper object validator when no scheme information is present.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.DefinitionID.txt

@@ -8,4 +8,4 @@ DEFAULT: NULL
     Unique identifier for a custom-built URI definition. If you  want
     to add custom URIFilters, you must specify this value.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.DefinitionRev.txt

@@ -8,4 +8,4 @@ DEFAULT: 1
     Revision identifier for your custom definition. See
     %HTML.DefinitionRev for details.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.Disable.txt

@@ -11,3 +11,4 @@ DEFAULT: false
 
 --ALIASES--
 Attr.DisableURI
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.DisableExternal.txt

@@ -8,3 +8,4 @@ and anti-pagerank-leech measure, but comes at a hefty price: nolinks or
 images outside of your domain will be allowed.  Non-linkified URIs will
 still be preserved.  If you want to be able to link to subdomains or use
 absolute URIs, specify %URI.Host for your website.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.DisableExternalResources.txt

@@ -10,3 +10,4 @@ forging, goatse.cx posting, and other nasties, but also results in a loss
 of end-user functionality (they can't directly post a pic they posted from
 Flickr anymore). Use it if you don't have a robust user-content moderation
 team.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.DisableResources.txt

@@ -9,4 +9,4 @@ DEFAULT: false
     still link to them though. See %URI.DisableExternalResources for why
     this might be a good idea.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.Host.txt

@@ -16,4 +16,4 @@ DEFAULT: NULL
     a given page may be on a sub-domain, but you wish HTML Purifier to be
     more relaxed and allow some of the parent domains too.
 </p>
-
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.HostBlacklist.txt

@@ -6,3 +6,4 @@ DEFAULT: array()
 List of strings that are forbidden in the host of any URI. Use it to kill
 domain names of spam, etc. Note that it will catch anything in the domain,
 so <tt>moo.com</tt> will catch <tt>moo.com.example.com</tt>.
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.MakeAbsolute.txt

@@ -10,3 +10,4 @@ DEFAULT: false
     viewed in a different context (and setting an alternate base URI is
     not possible). %URI.Base must be set for this directive to work.
 </p>
+--# vim: et sw=4 sts=4

library/HTMLPurifier/ConfigSchema/schema/URI.Munge.txt

@@ -80,3 +80,4 @@ DEFAULT: NULL
     was picked because it came after n (and I couldn't use a), p is for
     property.
 </p>
+--# vim: et sw=4 sts=4