summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/translation.mdwn14
1 files changed, 6 insertions, 8 deletions
diff --git a/doc/translation.mdwn b/doc/translation.mdwn
index 71e50cb1b..005d9c889 100644
--- a/doc/translation.mdwn
+++ b/doc/translation.mdwn
@@ -22,18 +22,13 @@ 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 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.
To generate the po and pot files for translating the basewiki,
- get ikiwiki's source, and edit the `basewikipo.setup` file,
- adding your language. Then run 'perl Makefile.PL; make basewikipo`.
+ get ikiwiki's source, and edit the `underlaypo.setup` file,
+ adding your language. Then run 'perl Makefile.PL; make underlaypo`.
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.
@@ -41,4 +36,7 @@ essentially three pieces needed for a complete translation:
`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.