2 > Here is my initial work on ikiwiki l10n infrastructure (I'm sending it
3 > before finalizing, there may be errors).
5 I've revised the patches (tested OK):
9 <http://people.debian.org/~roktas/patches/ikiwiki/ikiwiki-lang.diff>
11 + Support for CGI::FormBuilder.
12 + Modify Makefile.PL for l10n.
14 - l10n infrastructure from Koha project. (This patch must be applied with
15 '-p1', also, it needs a 'chmod +x l10n/*.pl' after patching.)
17 + Leave templates dir untouched, use a temporary translations directory
19 + Fix Makefile (it failed to update templates).
21 <http://people.debian.org/~roktas/patches/ikiwiki/ikiwiki-l10n.diff>
25 > fine. Also a final note, I haven't examined the quality of generated
28 Looks like, tmpl_process3 cannot preserve line breaks in template files.
29 For example, it processed the following template:
31 Someone[1], possibly you, requested that you be emailed the password for
33 <TMPL_VAR USER_NAME> on <TMPL_VAR WIKINAME>[2].
35 The password is: <TMPL_VAR USER_PASSWORD>
40 [1] The user requesting the password was at IP address <TMPL_VAR
42 [2] Located at <TMPL_VAR WIKIURL>
46 Birisi[1], ki muhtemelen bu sizsiniz, <TMPL_VAR WIKINAME>[2] üzerindeki
47 <TMPL_VAR USER_NAME> kullanıcısına ait parolanın epostalanması isteğinde
48 bulundu. Parola: <TMPL_VAR USER_PASSWORD> -- ikiwiki [1] Parolayı isteyen
49 kullanıcının ait IP adresi: <TMPL_VAR REMOTE_ADDR>[2] <TMPL_VAR WIKIURL>
51 > Looks like, tmpl_process3 cannot preserve line breaks in template files.
52 > For example, it processed the following template:
54 This could be easily worked around in tmpl_process3, but I wouldn't like to
55 maintain a separate utility.
59 As to the hardcoded strings in ikiwiki, I've internationalized the program,
60 and there is a po/ikiwiki.pot in the source that can be translated.
65 Danish l10n of templates and basewiki is available with the following commands:
67 git clone http://source.jones.dk/ikiwiki.git newsite
71 Updates are retrieved with this single command:
75 Right now the l10n is maintained by manually comparing against each new upstream release, and
76 updating both the master mirror and the l10n as needed.
78 Work is in progress to semi-automate this to still check manually for updates, but maintain the
79 l10n as PO files - to allow more translations to more than the few languages I know about myself.
81 As upstream ikiwiki is now maintained in GIT too, keeping the master mirror in sync with upstream
82 could probably be automated even more - but an obstacle seems to be that content is not maintained
83 separately but as an integral part of upstream source (GIT seems to not support subscribing to
84 only parts of a repository).
86 For example use, here's how to roll out a clone of the [Redpill support site](http://support.redpill.dk/):
88 mkdir -p ~/private_webdata
89 git clone http://source.redpill.dk/support.git ~/private_webdata/support.redpill.dk
90 cd ~/private_webdata/support.redpill.dk
92 mkdir -p ~/public_websites/support.redpill.dk
93 mkdir -p ~/public_websites/source.redpill.dk/support_content.git/hooks
94 mkdir -p ~/public_cgi/support.redpill.dk
97 (Redpill support is inspired by <http://help.riseup.net> but needs to be reusable for several similarly configured networks)