Unify modelines in Asciidoc files

This gets us close to using the same modeline in all files we run
through Asciidoc, as well as adding the spell and spelllang
declarations, just as we had in NEWS already.

The choice of 'en_us' is mainly for consistency and because the body of
work already uses these spellings.

Signed-off-by: Dan McGee <dan@archlinux.org>

HACKING

@@ -147,5 +147,5 @@ For example, to run valgrind:
     valgrind --leak-check=full -- src/pacman/.libs/lt-pacman -Syu
 
 /////
-vim: set ts=2 sw=2 syntax=asciidoc et:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////

doc/PKGBUILD.5.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 PKGBUILD(5)
 ===========

doc/footer.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 
 See the pacman website at http://www.archlinux.org/pacman/[] for current

doc/index.txt

@@ -107,9 +107,9 @@ link:ftp://ftp.archlinux.org/other/pacman/[]. To install, download the newest
 available source tarball, unpack it in a directory, and run the three magic
 commands:
 
-    $ ./configure
-    $ make
-    # make install
+	$ ./configure
+	$ make
+	# make install
 
 You may wish to read the options presented by `./configure --help` in order to
 set appropriate paths and build options that are correct for your system.
@@ -132,7 +132,7 @@ these trees).
 
 The current development tree can be fetched with the following command:
 
-    git clone git://projects.archlinux.org/pacman.git pacman
+	git clone git://projects.archlinux.org/pacman.git pacman
 
 which will fetch the full development history into a directory named pacman.
 You can browse the source as well using
@@ -206,5 +206,5 @@ pacman is Copyright (C) 2006-2011 Pacman Development Team
 version 2 or later.
 
 /////
-vim: set ts=2 sw=2 syntax=asciidoc et:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////

doc/libalpm.3.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 libalpm(3)
 ==========

doc/makepkg.8.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 makepkg(8)
 ==========

doc/makepkg.conf.5.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 makepkg.conf(5)
 ===============

doc/pacman-key.8.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 pacman-key(8)
 =============

doc/pacman.8.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 pacman(8)
 =========

doc/pacman.conf.5.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 pacman.conf(5)
 ==============

doc/pkgdelta.8.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 pkgdelta(8)
 =========

doc/repo-add.8.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 repo-add(8)
 ==========

doc/submitting-patches.txt

@@ -20,7 +20,7 @@ started with GIT if you have not worked with it before.
 
 The pacman code can be fetched using the following command:
 
-    git clone git://projects.archlinux.org/pacman.git
+	git clone git://projects.archlinux.org/pacman.git
 
 
 Creating your patch
@@ -32,7 +32,7 @@ Creating your patch
 The -s allows you to credit yourself by adding a "Signed Off By" line to
 indicate who has "signed" the patch - who has approved it.
 
-    Signed-off-by: Aaron Griffin <aaron@archlinux.org>
+	Signed-off-by: Aaron Griffin <aaron@archlinux.org>
 
 Please use your real name and email address. Feel free to "scramble" the
 address if you're afraid of spam.
@@ -94,5 +94,5 @@ aren't their own.
 --
 
 /////
-vim: set ts=2 sw=2 syntax=asciidoc et:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////

doc/translation-help.txt

@@ -40,15 +40,15 @@ not worried about any local translations being overwritten. The .tx/ directory
 is checked into the git repository so is preconfigured with the two project
 resources (See `tx status` output for a quick overview).
 
-    tx pull -f
-    poedit po/<mylang>.po
-    poedit lib/libalpm/po/<mylang>.po
-    tx push -t -l <mylang>
+	tx pull -f
+	poedit po/<mylang>.po
+	poedit lib/libalpm/po/<mylang>.po
+	tx push -t -l <mylang>
 
 Or to just push one of the two available resources:
 
-    tx push -r archlinux-pacman.pacman-pot -t -l fi
-    tx push -r archlinux-pacman.libalpm-pot -t -l fi
+	tx push -r archlinux-pacman.pacman-pot -t -l fi
+	tx push -r archlinux-pacman.libalpm-pot -t -l fi
 
 See the <<Notes,Notes>> section for additional hints on translating.
 
@@ -79,7 +79,7 @@ Incremental Updates
 If you have more advanced needs you will have to get a copy of the pacman
 repository.
 
-    git clone git://projects.archlinux.org/pacman.git pacman
+	git clone git://projects.archlinux.org/pacman.git pacman
 
 Next, you will need to run `./autogen.sh` and `./configure` in the base
 directory to generate the correct Makefiles. At this point, all necessary
@@ -91,11 +91,11 @@ We need to first update the main message catalog file. Navigate into either the
 work on first, and execute the following command.  If you are working in the
 `po/` tree, replace 'libalpm.pot' with 'pacman.pot':
 
-    make libalpm.pot-update
+	make libalpm.pot-update
 
 Next, update your specific language's translation file:
 
-    make <po file>-update
+	make <po file>-update
 
 At this point, you can do the translation. To submit your changes, either email
 the new `.po` file to the mailing-list with *[translation]* in the subject, or
@@ -104,7 +104,7 @@ submit a GIT-formatted patch (please do not include any `.pot` file changes).
 As a shortcut, all translation files (including `.pot` files) can be updated
 with the following command:
 
-    make update-po
+	make update-po
 
 Adding a New Language
 ~~~~~~~~~~~~~~~~~~~~~
@@ -133,16 +133,16 @@ msgid and msgstr 'variables' can be on as many lines as necessary. Line breaks
 are ignored- if you need a literal line break, use an `\n` in your string. The
 following two translations are equivalent:
 
-    msgstr "This is a test translation"
+	msgstr "This is a test translation"
 
-    msgstr ""
-    "This is a test translation"
+	msgstr ""
+	"This is a test translation"
 
 If you want to test the translation (for example, the frontend one):
 
-    rm *.gmo stamp-po
-    make
-    cp <lang code>.gmo /usr/share/locale/<lang code>/LC_MESSAGES/pacman.mo
+	rm *.gmo stamp-po
+	make
+	cp <lang code>.gmo /usr/share/locale/<lang code>/LC_MESSAGES/pacman.mo
 
 
 Translating Manpages
@@ -160,5 +160,5 @@ check there first before undergoing a translation effort to ensure you are not
 duplicating efforts.
 
 /////
-vim: set ts=2 sw=2 syntax=asciidoc et:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////

doc/vercmp.8.txt

@@ -1,5 +1,5 @@
 /////
-vim:set ts=4 sw=4 syntax=asciidoc noet:
+vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
 /////
 vercmp(8)
 =========