response

1 files changed, 13 insertions, 0 deletions

diff --git a/doc/bugs/ikiwiki_is_not_truly_localizable.mdwn b/doc/bugs/ikiwiki_is_not_truly_localizable.mdwn
index 1f519ddca..11bf1cab5 100644
--- a/doc/bugs/ikiwiki_is_not_truly_localizable.mdwn
+++ b/doc/bugs/ikiwiki_is_not_truly_localizable.mdwn
@@ -8,6 +8,12 @@ should be written as
 
 `my @buttons=(gettext("Save Page"), gettext("Preview"), gettext("Cancel"));`
 
+> Yes, these need to be fixed. But note that the localised texts come back
+> into ikiwiki and are used in various places, including plugins.
+> Including, possibly, third-party plugins. So localising the buttons would
+> seem to require converting from the translations back into the C locale
+> when the form is posted. --[[Joey]]
+
 In standards templates things seems wrongly written too. For instance in page.tmpl line like:
 
 `<li><a href="<TMPL_VAR EDITURL>" rel="nofollow">Edit</a></li>`
@@ -20,6 +26,13 @@ with EDITURL_TEXT variable initialized in Render.pm through a gettext call.
 
 Am I wrong ?
 
+> No, that's not a sane way to localise the templates. The templates can be
+> translated by making a copy and modifying it, or by using a tool to
+> generate .mo files from the templates, and generate translated templates
+> from .po files. (See [[todo/l10n]] for one attempt.) But pushing the
+> localisation of random strings in the templates through the ikiwiki
+> program defeats the purpose of having templates at all. --[[Joey]]
+
 If not I can spend some time preparing patches for such corrections if it can help.
 
 -- [[/users/bbb]]