summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-03-29 03:18:21 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-03-29 03:18:21 +0000
commite41dd1e24e345c974fe4a070088f0d09d1b6ddac (patch)
tree1e38ae17bb30573304f633ae9fe19dbf4935f562 /doc
parentbfe959167a9bad17cc23f9f8e9920aa2f2eaec1c (diff)
html validation fixes:
- escape & in urls (also clean up cgi url generation) - since markdown wraps inlined pages in <p></p>, close and re-open the paragraph tags when generating the embedded html - added XHTML 1.0 doctypes to templates - fixed <hr /> and <br /> in templates - add an alt attribute to inline images, based on the WikiLink to the image. Allows things like [[my_image|img.png]] to customise alt text.
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/html.mdwn31
1 files changed, 29 insertions, 2 deletions
diff --git a/doc/todo/html.mdwn b/doc/todo/html.mdwn
index ba167ea62..cb77774b5 100644
--- a/doc/todo/html.mdwn
+++ b/doc/todo/html.mdwn
@@ -6,8 +6,35 @@ editing the [[templates]] BTW.
Current problems:
- * A doctype should be added: do we want XHTML 1.0 or HTML 4.01 Trans as default?
- * If XHTML: In templates &lt;hr&gt; should become &lt;hr\&gt; etc.
+ * A doctype should be added: do we want XHTML 1.0 or HTML 4.01 Trans as
+ default?
+
+ Need to choose a doctype that corresponds to what [[MarkDown]]
+ generates. For example, it does generate &lt;hr /&gt;
+ So xhml seems a good fit and I'm going to add that to the
+ templates.
+
+ One consideration of course is that regular users might embed html
+ that uses deprecated presentational elements like &lt;center&gt;.
+ --[[Joey]]
+
+ * If XHTML: In templates &lt;hr&gt; should become &lt;hr /&gt; etc.
* Image wikilinks should provide an alt text (maybe '$filname wiki-image'?).
+
+ Now it will be the text of the [[WikiLink]], which even allows
+ setting a custom alt text like this: \[[my_alt_text|image.png]]
+ --[[Joey]]
+
* &'s in (cgi-)url's must be escaped as &amp;amp;.
+
+ Fixed --[[Joey]]
+
* [ [inlinepage] ] gets wrapped in &lt;p&gt;...&lt;/p&gt; which has a high chance of invalidating the page.
+
+ Since markdown does this, the only way I can think to fix it is to
+ make the inlined page text start with &lt;/p&gt; and end with
+ &lt;p&gt;. Ugly, and of course there could be problems with
+ markdown enclosing it in other spanning tags in some cases.
+ I've implemented this hack now. :-/ --[[Joey]]
+
+Test: [validate this page](http://validator.w3.org/check?url=referer)