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
20 The following adds a div element with class="trailer" around the meta-information
21 added after an inlined page (namely: the post date, the tags, and the actions):
23 --- inlinepage.tmpl.orig 2006-12-28 16:56:49.000000000 +0100
24 +++ inlinepage.tmpl 2006-12-28 17:02:06.000000000 +0100
29 +<div class="trailer">
31 <span class="pageinfo">
32 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]]
58 >>> I confirm that this ([[!debbug 405058]]) has just been fixed in markdown
59 >>> [`1.0.2b7`](http://packages.debian.org/experimental/web/markdown) (BTW, thanks to your bug
60 >>> report Joey). FYI, I've observed some performance drop with `1.0.2b7` compared to `1.0.1`,
61 >>> especially noticable with big files. This was also confirmed by someone else, for example,
62 >>> see this [thread](http://six.pairlist.net/pipermail/markdown-discuss/2006-August/000152.html)
65 >>>> 1.0.2b7 is slower, but ok, and parses much better. I'm waiting for it
66 >>>> to at least get into debian testing before I make ikiwiki depend on it
67 >>>> though. --[[Joey]]
69 >> This Markdown issue seems to have been worked around by the optimization
70 >> in which \[[!inline]] is replaced with a placeholder, and the
71 >> placeholder is later replaced by the HTML. Meanwhile, this patch
72 >> has been obsoleted by applying a similar one (wrapping things in a div
73 >> with class inlinefooter). That was the last remaining unapplied patch
74 >> on this page, so I think this whole page can be considered [[done]].
79 I'd like a class attribute on the `<span>` tag surrounding wikilinks
80 that refer to non-existent pages, in Ikiwiki.pm:htmllink, so that such
81 broken links can be styled more dramatically with CSS. --Jamey