summaryrefslogtreecommitdiff
path: root/doc/translation.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/translation.mdwn')
-rw-r--r--doc/translation.mdwn18
1 files changed, 14 insertions, 4 deletions
diff --git a/doc/translation.mdwn b/doc/translation.mdwn
index e3e458ce7..459f47eb5 100644
--- a/doc/translation.mdwn
+++ b/doc/translation.mdwn
@@ -22,11 +22,21 @@ essentially three pieces needed for a complete translation:
* The names and values of parameters, both to the program, in the setup
file, and in preprocessor directives.
+1. The [[basewiki]] needs to be translated. The
+ [[plugins/contrib/po]] ikiwiki plugin will allow translating
+ wikis using po files and can be used for this.
+
+ To generate the po and pot files for translating the basewiki,
+ get ikiwiki's source, edit the `po/underlay.setup` file,
+ adding your language. Then run 'make -C po underlays`.
+ This will generate many po files under `po/underlays`. The first
+ ones you'll want to translate are in the `po/underlays/basewiki` directory,
+ which is really not very large, just a few thousand words.
+ After that is done, you can tackle those under
+ `po/underlays/directives`, which are a much larger (tens of
+ thousands of words).
+
1. The templates also need to be translated. Some work has been done on an
infrastructure for maintaining translated templates, as documented in
[[todo/l10n]], but until that's complete, you'd need to copy and
translate the templates by hand.
-
-1. The [[basewiki]] itself needs to be translated. The
- [[plugins/contrib/po]] ikiwiki plugin will allow translating
- wikis using po files and can be used for this.