X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/de235168153178e148a9a474f609c3fb043bd1ea..0b89d442331bd62b4dc2da4f7fcbca59d5ca21eb:/doc/bugs/ikiwiki_is_not_truly_localizable.mdwn diff --git a/doc/bugs/ikiwiki_is_not_truly_localizable.mdwn b/doc/bugs/ikiwiki_is_not_truly_localizable.mdwn deleted file mode 100644 index a1b38257a..000000000 --- a/doc/bugs/ikiwiki_is_not_truly_localizable.mdwn +++ /dev/null @@ -1,47 +0,0 @@ -A lot of strings in ikiwiki are hardcoded and not taken for locales resources through gettext. This is bad because ikiwiki is thus difficult to spread for non-english users. - -I mean that, for instance in CGI.pm, line like: - -`my @buttons=("Save Page", "Preview", "Cancel");` - -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]] - ->> Wouldn't it be more easy to change all calls to the corrects ones (including in plugins) ? ->> For instance in the same file (CGI.pm): `elsif ($form->submitted eq gettext("Save Page")) {`. ->> That way no conversion to the C locale is needed. ->> gettext use should just be publicized in documentation (at least in [[plugins/write]]). --[[bbb]] - ->>> It would be easy, but it could break third-party plugins that hardcode ->>> the english strings. It's also probably less efficient to run gettext ->>> over and over. --[[Joey]] - -In standards templates things seems wrongly written too. For instance in page.tmpl line like: - -`