From e6a2f3ba6c205de7af4d53f64d353ee5c6795445 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 7 Nov 2007 13:57:11 -0500 Subject: web commit by tschwinge: Some ideas. --- doc/plugins/contrib/texinfo.mdwn | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) (limited to 'doc/plugins/contrib') diff --git a/doc/plugins/contrib/texinfo.mdwn b/doc/plugins/contrib/texinfo.mdwn index cb2bf038c..bc4939a92 100644 --- a/doc/plugins/contrib/texinfo.mdwn +++ b/doc/plugins/contrib/texinfo.mdwn @@ -27,14 +27,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 +55,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]] -- cgit v1.2.3 From 7cc90d84576de98e9d0728b671f6734dc5953109 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 7 Nov 2007 14:11:06 -0500 Subject: web commit by tschwinge: Why I wrote that plugin. --- doc/plugins/contrib/texinfo.mdwn | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'doc/plugins/contrib') diff --git a/doc/plugins/contrib/texinfo.mdwn b/doc/plugins/contrib/texinfo.mdwn index bc4939a92..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. -- cgit v1.2.3