Optimise use of gettext, and avoid ugly warnings if Locale::gettext is not available.

[git.ikiwiki.info.git] / doc / translation.mdwn

diff --git a/doc/translation.mdwn b/doc/translation.mdwn
index 58a8f4b48a521d678b5b6ad3d90d51f905af38b8..e3e458ce7487ecfcd058207ded6ff0dc018dd030 100644 (file)
--- a/doc/translation.mdwn
+++ b/doc/translation.mdwn
@@ -1,9 +1,9 @@
 If you want to translate your wiki into another language, there are
 If you want to translate your wiki into another language, there are

-essentailly three peices needed for a complete translation:
+essentially three pieces needed for a complete translation:

 
 1. The messages in the ikiwiki program itself need to be translated.
    Ikiwiki is internationalised, and most such messages are already marked
 
 1. The messages in the ikiwiki program itself need to be translated.
    Ikiwiki is internationalised, and most such messages are already marked

-   with `gettext()`. THe source tarball includes a creates a `po/ikiwiki.pot`
+   with `gettext()`. The source tarball includes a `po/ikiwiki.pot`

    that can be copied and translated as a po file. All very standard.
 
    Note that a few things in the source are not currently translated. These
    that can be copied and translated as a po file. All very standard.
 
    Note that a few things in the source are not currently translated. These


@@ -27,6 +27,6 @@ essentailly three peices needed for a complete translation:
    [[todo/l10n]], but until that's complete, you'd need to copy and
    translate the templates by hand.
 
    [[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. Whether to only translate
-   the page contents, or also translate the page names, is an open
-   question.
+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.