aboutsummaryrefslogtreecommitdiff
path: root/doc/plugins
diff options
context:
space:
mode:
authorJoey Hess <joey@wren.kitenet.net>2007-11-08 11:26:06 -0500
committerJoey Hess <joey@wren.kitenet.net>2007-11-08 11:26:06 -0500
commit0a4788456c16342c604d3cc402a8211b581b1d9d (patch)
treea80dc683052bb5b5b9baf012d953d8956caed5f2 /doc/plugins
parentb8deeaae4ddbc887f04fe417b72fa9bd5a93991e (diff)
downloadikiwiki-0a4788456c16342c604d3cc402a8211b581b1d9d.tar
ikiwiki-0a4788456c16342c604d3cc402a8211b581b1d9d.tar.gz
web commit by tschwinge: About M (M > 1) output files.
Diffstat (limited to 'doc/plugins')
-rw-r--r--doc/plugins/contrib/texinfo.mdwn15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/plugins/contrib/texinfo.mdwn b/doc/plugins/contrib/texinfo.mdwn
index fb5784812..e196d7089 100644
--- a/doc/plugins/contrib/texinfo.mdwn
+++ b/doc/plugins/contrib/texinfo.mdwn
@@ -59,6 +59,21 @@ is a N-to-M mapping:
> 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]]
+>> Currently I use `makeinfo --no-split` and render to stdout, so that I can
+>> easily capture the output and stuff it into the appropriate ikiwiki data structure.
+>> If we want to have multiple output files (which we'll eventually want to have,
+>> to avoid having such large single-file outputs), we won't be able to
+>> do this anymore.
+>> (?) Then we'll need a way to find the main output file, which
+>> will be the one to be copied into what ikiwiki expects to be the main output
+>> of the rendered `.texi` file.
+>> Perhaps (again) parse the `.texi` file for a `@setfilename` statement?
+>> The other generated files will also have to
+>> copied somewhere (preferably into a subdirectory named alike the main file
+>> to avoid name space collisions; but need to take care of links between the files then)
+>> and need to be registed within the ikiwiki system.
+>> --[[tschwinge]]
+
## `makeinfo` Output