X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/5dde5c7bc81752004c434ab9a8d9e87613078f52..1ca63edde0a1f09e58c9c1da1cf9ac7a6805750b:/doc/todo/language_definition_for_the_meta_plugin.mdwn diff --git a/doc/todo/language_definition_for_the_meta_plugin.mdwn b/doc/todo/language_definition_for_the_meta_plugin.mdwn index 817092863..33098c601 100644 --- a/doc/todo/language_definition_for_the_meta_plugin.mdwn +++ b/doc/todo/language_definition_for_the_meta_plugin.mdwn @@ -1,6 +1,5 @@ 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"]] +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 @@ -14,6 +13,38 @@ 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]] + 
 --- meta.orig.pm  2007-07-27 00:19:51.000000000 +0200
 +++ meta.pm       2007-08-05 22:37:40.000000000 +0200
@@ -47,5 +78,7 @@ This may be useful for sites with a few pages in different languages, but no ful
  } # }}}
+> Please resolve lang somewhere reusable rather than within meta plugin: It is certainly usable outside +> the scope of the meta plugin as well. --[[JonasSmedegaard]] -[[tag wishlist patch plugin/meta translation]] \ No newline at end of file +[[!tag wishlist patch plugins/meta translation]]