See the pacman website at http://www.archlinux.org/pacman/ for current
diff --git a/doc/index.txt b/doc/index.txt
index 4cc8313..5fd3f3b 100644
@@ -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
- $ ./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:
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.
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:
diff --git a/doc/translation-help.txt b/doc/translation-help.txt
index d95b513..ef86dbf 100644
@@ -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).
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 `
` 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):