From b50b23d85fdf2fd75627e7e656652aa9ef63ab83 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 6 Nov 2007 16:34:23 -0500 Subject: [PATCH] web commit by tschwinge: N-to-M mapping of input and output files. --- doc/plugins/contrib/texinfo.mdwn | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/doc/plugins/contrib/texinfo.mdwn b/doc/plugins/contrib/texinfo.mdwn index 46aa7acf9..d2d088a76 100644 --- a/doc/plugins/contrib/texinfo.mdwn +++ b/doc/plugins/contrib/texinfo.mdwn @@ -1,6 +1,27 @@ -[[I|tschwinge]] started writing a plugin to render [Texinfo](http://www.gnu.org/software/texinfo) +[[I|tschwinge]] started writing a plugin to render [Texinfo](http://www.gnu.org/software/texinfo/) inside the ikiwiki environment. The plugin is available at . It's very basic at the moment, but will be improved over time. + + +# Issues + +Conventional ikiwiki [[*htmlize*ing|plugins/write#index6h3]] +have a one-to-one mapping of input file and output file. +This can also be achieved for Texinfo files, but is somewhat +unusual there, when rendering them to HTML. In general, there +is a N-to-M mapping: + +* N Texinfo input files (a main `.texi` file, + several helper files (`fdl.texi`, `version.texi`, ...), and + additional text files which are included from the main `.texi` + file, e.g. `history.texi`, `libfoo.texi`, `libbar.texi`. +* M Texinfo output files: the main `.texi` file (which `include`s + the other input files) is usually rendered into a (flat) hierarchy + of HTML files, one file per node, see the table on + + for an example. + +How to teach this to ikiwiki?