1 I'm writing my own CSS for ikiwiki. During this effort I often found the need of adding more class="" attributes to the default ikiwiki templates. This way more presentational aspects of visual formatting can be delegated to CSS and removed from the HTML structure.
3 In this patch I plan to collect changes in this direction.
5 The first, one-liner, patch is to use a "div" element with a
6 class="actions" attribute for inline page as is done with non-inlined page.
7 This way the same CSS formatting can be applied to div.actions in the CSS,
8 while at the moment it must be duplicated for a span.actions (which I
9 believe is also incorrect, since it will contain a "ul" element, not sure
10 though). In case the markup should be differentiated it will still be
11 possible relying on the fact that a div.actions is contained or not in a
18 The following adds a div element with class="trailer" around the
19 meta-information added after an inlined page (namely: the post date, the
20 tags, and the actions):
22 The following adds a div element with class="trailer" around the meta-informati
23 on added after an inlined page (namely: the post date, the tags, and the actions):
25 --- inlinepage.tmpl.orig 2006-12-28 16:56:49.000000000 +0100
26 +++ inlinepage.tmpl 2006-12-28 17:02:06.000000000 +0100
31 +<div class="trailer">
33 <span class="pageinfo">
34 Posted <TMPL_VAR CTIME>
43 > Unfortunately, the inlinepage content passes through markdown, and markdown
44 > gets confused by these nested div's and puts p's around one of them, generating
45 > broken html. If you can come up with a way to put in the div that passes
46 > the test suite, or a fix to markdown, I will accept it, but the above patch
47 > fails the test suite. --[[Joey]]
49 >> Just a note... This discrepancy doesn't exist in [pandoc](http://code.google.com/p/pandoc/) as
50 >> demonstrated in the relevant [page](http://code.google.com/p/pandoc/wiki/PandocVsMarkdownPl).
51 >> Pandoc is a _real parser_ for markdown (contrasting the regexp based implementation of
52 >> markdown.pl). I've almost finished the Debian packaging. John is working on a `--strict` mode
53 >> which will hopefully make pandoc a drop-in replacement for markdown. I'll upload pandoc after
54 >> his work has finished. Whether it could be used in IkiWiki is an open question, but having
55 >> alternatives is always a good thing and perhaps, the fact that pandoc can make markdown->LaTeX
56 >> conversion may lead to new possibilities. --[[Roktas]]