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. 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 => { 'code' => 'en', 'name' => 'English' }
54 `po_slave_languages` is used to set the list of supported "slave"
57 po_slave_languages => { 'fr' => 'Français',
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, one has to set `DirectoryIndex index` for
123 Setting `DefaultLanguage LL` (replace `LL` with your default MIME
124 language code) for the wiki context can help to ensure
125 `bla/page/index.en.html` is served as `Content-Language: LL`.
127 For details, see [Apache's documentation](http://httpd.apache.org/docs/2.2/content-negotiation.html).
132 Recent versions of lighttpd should be able to use
133 `$HTTP["language"]` to configure the translatted pages to be served.
135 See [Lighttpd Issue](http://redmine.lighttpd.net/issues/show/1119)
145 When `po_link_to` is not set to `negotiated`, one should replace some
146 occurrences of `BASEURL` with `HOMEPAGEURL` to get correct links to
149 The `ISTRANSLATION` and `ISTRANSLATABLE` variables can be used to
150 display things only on translatable or translation pages.
152 ### Display page's versions in other languages
154 The `OTHERLANGUAGES` loop provides ways to display other languages'
155 versions of the same page, and the translations' status.
157 An example of its use can be found in the default
158 `templates/page.tmpl`. In case you want to customize it, the following
159 variables are available inside the loop (for every page in):
161 * `URL` - url to the page
162 * `CODE` - two-letters language code
163 * `LANGUAGE` - language name (as defined in `po_slave_languages`)
164 * `MASTER` - is true (1) if, and only if the page is a "master" page
165 * `PERCENT` - for "slave" pages, is set to the translation completeness, in percents
167 ### Display the current translation status
169 The `PERCENTTRANSLATED` variable is set to the translation
170 completeness, expressed in percent, on "slave" pages. It is used by
171 the default `templates/page.tmpl`.
173 Additional PageSpec tests
174 -------------------------
176 This plugin enhances the regular [[ikiwiki/PageSpec]] syntax with some
177 additional tests that are documented [[here|ikiwiki/pagespec/po]].
179 Automatic PO file update
180 ------------------------
182 Committing changes to a "master" page:
184 1. updates the POT file and the PO files for the "slave" languages;
185 the updated PO files are then put under version control;
186 2. triggers a refresh of the corresponding HTML slave pages.
188 Also, when the plugin has just been enabled, or when a page has just
189 been declared as being translatable, the needed POT and PO files are
190 created, and the PO files are checked into version control.
192 Discussion pages and other sub-pages
193 ------------------------------------
195 Discussion should happen in the language in which the pages are
196 written for real, *i.e.* the "master" one. If discussion pages are
197 enabled, "slave" pages therefore link to the "master" page's
200 Likewise, "slave" pages are not supposed to have sub-pages;
201 [[WikiLinks|wikilink]] that appear on a "slave" page therefore link to
202 the master page's sub-pages.
207 One can edit the PO files using ikiwiki's CGI (a message-by-message
208 interface could also be implemented at some point).
210 If [[tips/untrusted_git_push]] is setup, one can edit the PO files in one's
211 preferred `$EDITOR`, without needing to be online.
213 Markup languages support
214 ------------------------
216 [[Markdown|mdwn]] is well supported. Some other markup languages supported
217 by ikiwiki mostly work, but some pieces of syntax are not rendered
218 correctly on the slave pages:
220 * [[reStructuredText|rst]]: anonymous hyperlinks and internal
222 * [[wikitext]]: conversion of newlines to paragraphs
223 * [[creole]]: verbatim text is wrapped, tables are broken
224 * [[html]] and LaTeX: not supported yet; the dedicated po4a modules
225 could be used to support them, but they would need a security audit
226 * other markup languages have not been tested.
231 [[po/discussion]] contains a detailed security analysis of this plugin
232 and its dependencies.
234 When using po4a older than 0.35, it is recommended to uninstall
235 `Text::WrapI18N` (Debian package `libtext-wrapi18n-perl`), in order to
236 avoid a potential denial of service.
245 [[bugs/pagetitle_function_does_not_respect_meta_titles]] from
246 [[intrigeri]]'s `meta` branch is merged into ikiwiki upstream, the
247 generated links' text will be optionally based on the page titles set
248 with the [[meta|plugins/meta]] plugin, and will thus be translatable.
249 It will also allow displaying the translation status in links to slave
250 pages. Both were implemented, and reverted in commit
251 ea753782b222bf4ba2fb4683b6363afdd9055b64, which should be reverted
252 once [[intrigeri]]'s `meta` branch is merged.
254 An integration branch, called `meta-po`, merges [[intrigeri]]'s `po`
255 and `meta` branches, and thus has this additional features.
257 Language display order
258 ----------------------
260 Jonas pointed out that one might want to control the order that links to
261 other languages are listed, for various reasons. Currently, there is no
262 order, as `po_slave_languages` is a hash. It would need to be converted
263 to an array to support this. (If twere done, twere best done quickly.)
266 > Done in my po branch, preserving backward compatibility. Please
267 > review :) --[[intrigeri]]
272 I was suprised that, when using the map directive, a pagespec of "*"
273 listed all the translated pages as well as regular pages. That can
274 make a big difference to an existing wiki when po is turned on,
275 and seems generally not wanted.
276 (OTOH, you do want to match translated pages by
277 default when locking pages.) --[[Joey]]
279 Edit links on untranslated pages
280 --------------------------------
282 If a page is not translated yet, the "translated" version of it
283 displays wikilinks to other, existing (but not yet translated?)
284 pages as edit links, as if those pages do not exist.
286 That's really confusing, especially as clicking such a link
287 brings up an edit form to create a new, english page.
289 This is with po_link_to=current or negotiated. With default, it doesn't
292 Also, this may only happen if the page being linked to is coming from an
293 underlay, and the underlays lack translation to a given language.
296 > Any simple testcase to reproduce it, please? I've never seen this
297 > happen yet. --[[intrigeri]]
299 >> Sure, go here <http://l10n.ikiwiki.info/smiley/smileys/index.sv.html>
300 >> (Currently 0% translateed) and see the 'WikiLink' link at the bottom,
301 >> which goes to <http://l10n.ikiwiki.info/ikiwiki.cgi?page=ikiwiki/wikilink&from=smiley/smileys&do=create>
302 >> Compare with eg, the 100% translated Dansk version, where
303 >> the WikiLink link links to the English WikiLink page. --[[Joey]]
305 Double commits of po files
306 --------------------------
308 When adding a new english page, the po files are created, committed,
309 and then committed again. The second commit makes this change:
311 -"Content-Type: text/plain; charset=utf-8\n"
312 -"Content-Transfer-Encoding: ENCODING"
313 +"Content-Type: text/plain; charset=UTF-8\n"
314 +"Content-Transfer-Encoding: ENCODING\n"
316 Same thing happens when a change to an existing page triggers a po file
319 > * The s/utf-8/UTF-8 part is fixed in my po branch.
320 > * The ENCODING\n part is due to an inconsistency in po4a, which
321 > I've just send a patch for. --[[intrigeri]]
323 Ugly messages with empty files
324 ------------------------------
326 If there are empty .mdwn files, the po plugin displays some ugly messages.
328 > This is due to a bug in po4a (not checking definedness of a
329 > variable). One-liner patch sent. --[[intrigeri]]
331 Translation of directives
332 -------------------------
334 If a translated page contains a directive, it may expand to some english
335 text, or text in whatever single language ikiwiki is configured to "speak".
337 Maybe there could be a way to switch ikiwiki to speaking another language
338 when building a non-english page? Then the directives would get translated.
340 (We also will need this in order to use translated templates, when they are
346 Maybe write separate documentation depending on the people it targets:
347 translators, wiki administrators, hackers. This plugin may be complex
348 enough to deserve this.