diff --git a/doc/plugins/contrib/texinfo.mdwn b/doc/plugins/contrib/texinfo.mdwn index cb2bf038c..5ea3bb144 100644 --- a/doc/plugins/contrib/texinfo.mdwn +++ b/doc/plugins/contrib/texinfo.mdwn @@ -1,6 +1,11 @@ -[[I|tschwinge]] started writing a plugin to render [Texinfo](http://www.gnu.org/software/texinfo/) +[[I|tschwinge]] started writing a plugin to render +[GNU Texinfo](http://www.gnu.org/software/texinfo/) inside the ikiwiki environment. +This plugin is not neccessarily meant to enable people to write arbitrary +wiki pages in the Texinfo format (even though that is possible, of course), +but rather to ease collaboration on existing Texinfo documents. + The plugin is available at . It's very basic at the moment, but will be improved over time. @@ -27,14 +32,22 @@ is a N-to-M mapping: for an example. -How to teach this to ikiwiki? +How to teach this to ikiwiki? --[[tschwinge]] > As far as multiple input files, you'd need to use add_depends() > to let ikiwiki know that a change to any of those files should cause a -> rebuild of the "main" file. I guess you'd also have to somehow deal with +> rebuild of the "main" file. --[[Joey]] + +>> I'll see about a frob to get `makeinfo` provide me with a list of files +>> it used for rendering a given `.texi` file. --[[tschwinge]] + +> I guess you'd also have to somehow deal with > it wanting to render pages for each of the helper files. Not quite sure -> what the best way would be to avoid that. -> +> what the best way would be to avoid that. --[[Joey]] + +>> Might it be an option to simply not render the pages that are already +>> being used as an `include` file for another `.texi` file? --[[tschwinge]] + > Ikiwiki is perfectly happy with a page creating other files (see eg, the > img and teximg plugins, as well as the inline plugin's rss generation). > The will_render() function supports that. @@ -47,13 +60,14 @@ How to teach this to ikiwiki? > appear in a site map, be linked to, etc). Not sure how to do that, > and perhaps you could get away without doing it actually. --[[Joey]] + ## Copyright and Licensing Snippets ikiwiki (obviously) doesn't understand (parse) the copyright and licensing -statements which are included in `.texi` files. +statements which are included in `.texi` files. --[[tschwinge]] ## `makeinfo` Output `makeinfo --html` is being used for rendering. It creates stand-alone -HTML files, while ikiwiki only needs the files' ``s. +HTML files, while ikiwiki only needs the files' ``s. --[[tschwinge]] diff --git a/doc/plugins/meta/discussion.mdwn b/doc/plugins/meta/discussion.mdwn index 0c9e121ac..73114a951 100644 --- a/doc/plugins/meta/discussion.mdwn +++ b/doc/plugins/meta/discussion.mdwn @@ -13,3 +13,6 @@ Now I've work-arounded it using apostrophes in another way > As with any other parameter in a [[preprocessordirective]], you can > triple-quote, and then include quotation marks inside. --[[Joey]] + +>> Thanks for the hint! Toggle plugin is probably my favourite ikiwiki +>> plugin, but I forget about that :D --[[Paweł|ptecza]] \ No newline at end of file diff --git a/doc/todo/Configureable_separator_of_page_name.mdwn b/doc/todo/Configureable_separator_of_page_name.mdwn index 82343de63..8f4500d89 100644 --- a/doc/todo/Configureable_separator_of_page_name.mdwn +++ b/doc/todo/Configureable_separator_of_page_name.mdwn @@ -7,3 +7,6 @@ character in ikiwiki? > To do this a plugin could overwride the builtin IkiWiki::pagetitle, > IkiWiki::titlepage, and IkiWiki::linkpage functions. All the mangling of > page names should be cantralised to those functions. --[[Joey]] + +>> Do I really need a plugin to do it? What about yet another parameter +>> for `ikiwiki.setup` file? ;) --[[Paweł|ptecza]] \ No newline at end of file