1 [[!template id=plugin name=linguas author="Jordà Polo"]]
6 Linguas is a plugin for [ikiwiki](http://ikiwiki.info/) that
7 allows translations of wiki pages.
9 Download: [linguas.pm](http://ettin.org/pub/ikiwiki/linguas.pm) (2006-08-21).
11 Note that even though it is still available for download, this plugin is no
12 longer actively maintained. If you are interested in multilingual wiki pages, you
13 can also take a look at other approaches such as [[todo/l10n]] or Lars Wirzenius's
14 [Static website, with translations, using IkiWiki](http://liw.iki.fi/liw/log/2007-05.html#20070528b).
19 Translatable pages and translations must have the following format:
20 `pagename.$LANG`, where `$LANG` is a ISO639-1 (two-letter) language code.
21 To enable linguas, add the following line in the source code of the page:
25 Note that linguas is only required in one of the pages (the original,
26 for instance); the rest of translations will be automatically
27 updated. Additionally, it is also possible to specify the title of
30 \[[linguas title="Translated title"]]
36 This is the template code that should be added to `templates/page.tmpl`:
38 <TMPL_IF NAME="LINGUAS">
40 <p class="otherlinguas"><TMPL_VAR NAME="OTHERLINGUAS"></p>
42 <TMPL_LOOP NAME="LINGUAS">
43 <li><TMPL_VAR NAME=LINK></li>
53 * The current language list only contains 4 languages (ca, de, en,
54 es), and is "hardcoded" in linguas.pm. Would be interesting to define
55 it in ikiwiki.setup, though some problems were found while trying to do
56 so. (Actually, defining hash-like arguments from the command like works
57 fine, but it fails from ikiwiki.setup.)
59 > My guess about this is that it's because of the way Setup/Standard.pm
60 > untaints the config items from the file. It has code to handle arrays,
61 > but not hashes or more complex data structures. --[[Joey]]
63 > > Right. With this simple
64 > > [patch](http://ettin.org/pub/ikiwiki/hash_setup.patch) it seems to
65 > > work. However, note that 1) it only allows simple hashes, hashes of
66 > > hashes will not work (I don't think getops can handle complex hashes
67 > > anyway); 2) I don't really know when/why you call
68 > > `possibly_foolish_untaint()`; and 3) I'm no perl guru ;). --Jordà
70 > > > It's good. Applied..
72 * Wiki links to other translated pages require the full page name
73 including the `.$LANG`. It should be possible to link automatically
74 to pages with the same `.$LANG`, but that would probably require some
75 changes in IkiWiki. (I'm not sure though, I still haven't looked at
78 > Have you considered using the form ll/page? This would let more usual
79 > linking rules apply amoung pages without needing to specify the
80 > language. I'm not sure if you're supporting browser content
81 > negotiation, or whether that other layout would be harder to support it
84 > > Actually, I'm happy with the way it works now (and yeah, it is very
85 > > easy to take advantage of content negotiation). I just wanted
86 > > something simple to translatte a single page (or a few pages), not
87 > > the entire wiki. I'm not even sure it is a good idea to have fully
88 > > multilingual wikis, in most cases I would go for a different wiki
89 > > for each language. That said, I think it is an interesting idea, so
90 > > I'll take a look when I have the time. Thanks for your comments.
93 * The changes to htmllink in ikiwiki 1.44 broke this plugin.
94 The following fixes it:
96 --- linguas.pm.orig 2006-08-23 19:07:04.000000000 +0200
97 +++ linguas.pm 2007-03-24 01:53:18.000000000 +0100
99 if (exists $linguas{$2} && defined $linguas{$2}) {
100 $link = $linguas{$2}{'name'};
102 - push @links, IkiWiki::htmllink($page, $destpage, $trans, 0, 0, $link);
103 + push @links, IkiWiki::htmllink($page, $destpage, $trans, noimageinline => 0, forcesubpage => 0, linktext => $link);
106 my $otherlinguas = 'Translations:';