X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/4678e1a79daa5d2e66960723e9cae8531c72bf67..12eb056b33e1f01a63c4fcee408c9ac0d96c6b5e:/doc/todo/BibTeX.mdwn diff --git a/doc/todo/BibTeX.mdwn b/doc/todo/BibTeX.mdwn index d80cc895f..1ac9e99b8 100644 --- a/doc/todo/BibTeX.mdwn +++ b/doc/todo/BibTeX.mdwn @@ -20,4 +20,53 @@ Feel free to propose any modifications to enhance this plugin. --[[AlexandreDupas]] -[[tag soc]] [[tag wishlist]] +I have not found any other approach to build several wiki page with only one source file. Does someone have an idea? + +I also try to build a wiki-wide preprocessing of the source file to find reference to my bib entry (citation) but apparently there is no wiki-wide preprocessing hook allowing to collect data from each page before building the site. Do I miss something? + +--[[AlexandreDupas]] + +> The scan hook is run on new page content before building --[[Joey]] + +What notation did you have in mind for citations? A preprocessor +directive? Something LaTeX-inspired might be + + \[[!cite key="foo"]] + +which would output "(Foo, 2008)". With the appropriate options, this +could allow for several variations like "Foo (2008)" and "(Foo, 2008, +p. 28)". A `nocite` option could cause the reference to be printed in +the bibliography but produce no output. + +What about the references section? There are several ways to +go about it, for example: + +1. It could be included at the bottom of the page automatically for + pages with references, with a configurable title and heading level + (e.g., `

References

`) followed by a list of references. + +2. Use another preprocessor directive like + + ## References ## + + \[[!bibliography ]] + + or + + \[[!bibliography title="References" headerlevel="2"]] + + with configurable default values. Would it be tedious to do this on + every page? + +3. Use HTML::Template and allow users to add a bibliography section to + `page.tmpl` to include the bibliography if references are present and + loop over the references to emit a list. The downside here is having + to ask people to modify their templates (unless the plugin is + eventually included in the distribution). + +Any thoughts on the best way to proceed? + +--[[JasonBlevins]], March 23, 2008 21:41 EDT + + +[[!tag soc]] [[!tag wishlist]]