1 Make the html valid. Add css and prettify. Make RecentChanges use table for
2 formatting, and images to indicate web vs svn commits and to link to diffs.
4 All of this should be doable w/o touching a single line of code, just
5 editing the [[templates]] BTW.
9 * A doctype should be added: do we want XHTML 1.0 or HTML 4.01 Trans as
12 Need to choose a doctype that corresponds to what [[MarkDown]]
13 generates. For example, it does generate <hr />
14 So xhml seems a good fit and I'm going to add that to the
17 One consideration of course is that regular users might embed html
18 that uses deprecated presentational elements like <center>.
21 * If XHTML: In templates <hr> should become <hr /> etc.
22 * Image wikilinks should provide an alt text (maybe '$filname wiki-image'?).
24 Now it will be the text of the [[WikiLink]], which even allows
25 setting a custom alt text like this: \[[my_alt_text|image.png]]
28 * &'s in (cgi-)url's must be escaped as &amp;.
32 * [ [inlinepage] ] gets wrapped in <p>...</p> which has a high chance of invalidating the page.
34 Since markdown does this, the only way I can think to fix it is to
35 make the inlined page text start with </p> and end with
36 <p>. Ugly, and of course there could be problems with
37 markdown enclosing it in other spanning tags in some cases.
38 I've implemented this hack now. :-/ --[[Joey]]
40 Test: [validate this page](http://validator.w3.org/check?url=referer)