Here is a patch for the [[plugins/meta]] plugin. It adds the possibility to define the language used for a page, with \[[!meta lang="ja"]] It doesn't insert the langage information in the xhtml meta elements, but defines a LANG variable to use in the templates, for example with fr" xml:lang="fr"> This way also allows to define a language for a subset of the final page, with custom templates and inclusion. This may be useful for sites with a few pages in different languages, but no full i18n. > Looks good, but the need to modify the template and include a default > language in it is a bit problimatic, I think. --[[Joey]] >> --lang=XX could be a setup option, with a default value, then the template would be >>> Yes, that seems reasonable. I guess there's no problem with defaulting >>> to en if it can be overridden in the setup. --[[Joey]] >>>> Yes, english default makes sense. I guess we should use the `$config{lang}`, >>>> defined from the setup file or command-line options to define the default language >>>> (`$config{lang}` defaults to `en` which is fine) if the html pages, and override >>>> it from the `meta` directive. >>>> — [[NicolasLimare]] >>>>> ikiwiki already has a $config{locale}, which is a full locale (ie, >>>>> "en_US.UTF-8". This just needs to be parsed for the lang. --[[Joey]] >>>>>> My mistake, I meant $config{locale} --[[NicolasLimare]] > So the patch below could be changed to parse `$config{locale}` for the > language, and pass it if no specific lang was set for the page. The only > problem with that would be that this is all done inside the meta plugin, > so if that plugin were disabled, the lang would be empty. To avoid that, > I guess that the template needs to look like: lang="" xml:lang=""> > Now it just needs to be finished up.. --[[Joey]]
---  2007-07-27 00:19:51.000000000 +0200
+++       2007-08-05 22:37:40.000000000 +0200
@@ -11,6 +11,7 @@
 my %permalink;
 my %author;
 my %authorurl;
+my %lang;
 sub import {
        hook(type => "preprocess", id => "meta", call => \&preprocess, scan => 1);
@@ -100,6 +101,11 @@
+       elsif ($key eq 'lang') {
+           if ($value =~ /^[A-Za-z]{2}$/) {
+               $lang{$page}=$value;
+           }
+       }
        else {
@@ -131,6 +137,8 @@
                if exists $author{$page} && $template->query(name => "author");
        $template->param(authorurl => $authorurl{$page})
                if exists $authorurl{$page} && $template->query(name => "authorurl");
+       $template->param(lang => $lang{$page})
+               if exists $lang{$page} && $template->query(name => "lang");
> Please resolve lang somewhere reusable rather than within meta plugin: It is certainly usable outside > the scope of the meta plugin as well. --[[JonasSmedegaard]] >> I don't see any problem with having this in meta? meta is on by default, and >> other plugins are free to use it or even depend on it (e.g. inline does). >> >> My only comments on this patch beyond what Joey said are that the page >> language could usefully go into `$pagestate{$page}{meta}{lang}` for other >> plugins to be able to see it (is that what you meant?), and that >> restricting to 2 characters is too restrictive (HTML 4.01 mentions >> `en`, `en-US` and `i-navajo` as possible language codes). >> This slightly complicates parsing the locale to get the default language: >> it'll need `tr/_/-/` after the optional `.encoding` is removed. >> --[[smcv]] [[!tag wishlist patch plugins/meta translation]]