aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2008-03-23 22:08:02 -0400
committerJoey Hess <joey@kitenet.net>2008-03-23 22:08:02 -0400
commitafab05a505e3edce906e66781e9748a9e2ab1334 (patch)
treeeef5e5bb4facb17883876bb1cad1db48729a4eb1
parentcb8d1c86425999eb3572326679fae9a033664150 (diff)
downloadikiwiki-afab05a505e3edce906e66781e9748a9e2ab1334.tar
ikiwiki-afab05a505e3edce906e66781e9748a9e2ab1334.tar.gz
web commit by http://jblevins.org/: Thoughts about notation for citations
-rw-r--r--doc/todo/BibTeX.mdwn41
1 files changed, 41 insertions, 0 deletions
diff --git a/doc/todo/BibTeX.mdwn b/doc/todo/BibTeX.mdwn
index d471b0e82..1ab0b2e81 100644
--- a/doc/todo/BibTeX.mdwn
+++ b/doc/todo/BibTeX.mdwn
@@ -28,4 +28,45 @@ I also try to build a wiki-wide preprocessing of the source file to find referen
> 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., `<h2>References</h2>`) 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]]