1 [[!template id=plugin name=po core=0 author="[[intrigeri]]"]]
4 This plugin adds support for multi-lingual wikis, translated with
5 gettext, using [po4a](http://po4a.alioth.debian.org/).
7 It depends on the Perl `Locale::Po4a::Po` library (`apt-get install po4a`).
8 As detailed bellow in the security section, `po4a` is subject to
9 denial-of-service attacks before version 0.35.
16 A language is chosen as the "master" one, and any other supported
17 language is a "slave" one.
19 A page written in the "master" language is a "master" page. It can be
20 of any page type supported by ikiwiki, except `po`. It does not have to be
21 named a special way: migration to this plugin does not imply any page
24 Example: `bla/page.mdwn` is a "master" Markdown page written in
25 English; if `usedirs` is enabled, it is rendered as
26 `bla/page/index.en.html`, else as `bla/page.en.html`.
28 Any translation of a "master" page into a "slave" language is called
29 a "slave" page; it is written in the gettext PO format. `po` is now
30 a page type supported by ikiwiki.
32 Example: `bla/page.fr.po` is the PO "message catalog" used to
33 translate `bla/page.mdwn` into French; if `usedirs` is enabled, it is
34 rendered as `bla/page/index.fr.html`, else as `bla/page.fr.html`
39 This plugin does not support the `indexpages` mode (a.k.a. "use page/index.mdwn source files"). If you don't know
40 what it is, you probably don't care.
49 `po_master_language` is used to set the "master" language in
50 `ikiwiki.setup`, such as:
52 po_master_language: en|English
54 `po_slave_languages` is used to set the list of supported "slave"
62 Decide which pages are translatable
63 -----------------------------------
65 The `po_translatable_pages` setting configures what pages are
66 translatable. It is a [[ikiwiki/PageSpec]], so you have lots of
67 control over what kind of pages are translatable.
69 The `.po` files are not considered as being translatable, so you don't need to
70 worry about excluding them explicitly from this [[ikiwiki/PageSpec]].
77 The `po_link_to` option in `ikiwiki.setup` is used to decide how
78 internal links should be generated, depending on web server features
79 and site-specific preferences.
81 #### Default linking behavior
83 If `po_link_to` is unset, or set to `default`, ikiwiki's default
84 linking behavior is preserved: `\[[destpage]]` links to the master
87 #### Link to current language
89 If `po_link_to` is set to `current`, `\[[destpage]]` links to the
90 `destpage`'s version written in the current page's language, if
93 * `foo/destpage/index.LL.html` if `usedirs` is enabled
94 * `foo/destpage.LL.html` if `usedirs` is disabled
96 #### Link to negotiated language
98 If `po_link_to` is set to `negotiated`, `\[[page]]` links to the
99 negotiated preferred language, *i.e.* `foo/page/`.
101 (In)compatibility notes:
103 * if `usedirs` is disabled, it does not make sense to set `po_link_to`
104 to `negotiated`; this option combination is neither implemented
106 * if the web server does not support Content Negotiation, setting
107 `po_link_to` to `negotiated` will produce a unusable website.
115 Using Apache `mod_negotiation` makes it really easy to have Apache
116 serve any page in the client's preferred language, if available.
118 Add 'Options MultiViews' to the wiki directory's configuration in Apache.
120 When `usedirs` is enabled, you should also set `DirectoryIndex index`.
122 These settings are also recommended, in order to avoid serving up rss files
125 AddType application/rss+xml;qs=0.8 .rss
126 AddType application/atom+xml;qs=0.8 .atom
128 For details, see [Apache's documentation](http://httpd.apache.org/docs/2.2/content-negotiation.html).
133 Recent versions of lighttpd should be able to use
134 `$HTTP["language"]` to configure the translated pages to be served.
136 See [Lighttpd Issue](http://redmine.lighttpd.net/issues/show/1119)
146 When `po_link_to` is not set to `negotiated`, one should replace some
147 occurrences of `BASEURL` with `HOMEPAGEURL` to get correct links to
150 The `ISTRANSLATION` and `ISTRANSLATABLE` variables can be used to
151 display things only on translatable or translation pages.
153 The `LANG_CODE` and `LANG_NAME` variables can respectively be used to
154 display the current page's language code and pretty name.
156 ### Display page's versions in other languages
158 The `OTHERLANGUAGES` loop provides ways to display other languages'
159 versions of the same page, and the translations' status.
161 An example of its use can be found in the default
162 `templates/page.tmpl`. In case you want to customize it, the following
163 variables are available inside the loop (for every page in):
165 * `URL` - url to the page
166 * `CODE` - two-letters language code
167 * `LANGUAGE` - language name (as defined in `po_slave_languages`)
168 * `MASTER` - is true (1) if, and only if the page is a "master" page
169 * `PERCENT` - for "slave" pages, is set to the translation completeness, in percents
171 ### Display the current translation status
173 The `PERCENTTRANSLATED` variable is set to the translation
174 completeness, expressed in percent, on "slave" pages. It is used by
175 the default `templates/page.tmpl`.
177 Additional PageSpec tests
178 -------------------------
180 This plugin enhances the regular [[ikiwiki/PageSpec]] syntax with some
181 additional tests that are documented [[here|ikiwiki/pagespec/po]].
183 Automatic PO file update
184 ------------------------
186 Committing changes to a "master" page:
188 1. updates the POT file and the PO files for the "slave" languages;
189 the updated PO files are then put under version control;
190 2. triggers a refresh of the corresponding HTML slave pages.
192 Also, when the plugin has just been enabled, or when a page has just
193 been declared as being translatable, the needed POT and PO files are
194 created, and the PO files are checked into version control.
196 Discussion pages and other sub-pages
197 ------------------------------------
199 Discussion should happen in the language in which the pages are
200 written for real, *i.e.* the "master" one. If discussion pages are
201 enabled, "slave" pages therefore link to the "master" page's
204 Likewise, "slave" pages are not supposed to have sub-pages;
205 [[WikiLinks|ikiwiki/wikilink]] that appear on a "slave" page therefore link to
206 the master page's sub-pages.
211 One can edit the PO files using ikiwiki's CGI (a message-by-message
212 interface could also be implemented at some point).
214 If [[tips/untrusted_git_push]] is setup, one can edit the PO files in one's
215 preferred `$EDITOR`, without needing to be online.
217 Markup languages support
218 ------------------------
220 [[Markdown|mdwn]] and [[html]] are well supported. Some other markup
221 languages supported by ikiwiki mostly work, but some pieces of syntax
222 are not rendered correctly on the slave pages:
224 * [[reStructuredText|rst]]: anonymous hyperlinks and internal
226 * [[wikitext]]: conversion of newlines to paragraphs
227 * [[creole]]: verbatim text is wrapped, tables are broken
228 * LaTeX: not supported yet; the dedicated po4a module
229 could be used to support it, but it would need a security audit
230 * other markup languages have not been tested.
235 A translatable page may be renamed using the web interface and the
236 [[rename plugin|plugins/rename]], or using the VCS directly; in
237 the latter case, *both* the "master" page and every corresponding
238 `.po` file must be renamed in the same commit.
243 [[po/discussion]] contains a detailed security analysis of this plugin
244 and its dependencies.
246 When using po4a older than 0.35, it is recommended to uninstall
247 `Text::WrapI18N` (Debian package `libtext-wrapi18n-perl`), in order to
248 avoid a potential denial of service.
253 [[!inline pages="bugs/po:* and !bugs/done and !link(bugs/done) and !bugs/*/*"
254 feeds=no actions=no archive=yes show=0]]
259 [[!inline pages="todo/po:* and !todo/done and !link(todo/done) and !todo/*/*"
260 feeds=no actions=no archive=yes show=0]]