web commit by joey

[ikiwiki.git] / doc / todo / html.mdwn

diff --git a/doc/todo/html.mdwn b/doc/todo/html.mdwn
index 0d09e0158d3c53a4084cc08c1009e89e89adca50..b22e75283a465fac83f7fe2a9e84642ac6e6e16e 100644 (file)
--- a/doc/todo/html.mdwn
+++ b/doc/todo/html.mdwn
@@ -28,8 +28,16 @@ editing the [[templates]] and/or editing [[style.css]] BTW.
        This prevents markdown enclosing and even adds a useful css identifier. Problem is that this should be added to every page and not in the template(s). --[[JeroenSchot]]
 
        I can make ikiwiki add that around every inlined page easily
-       enough. However, where is it docuemented? Came up dry on google.
+       enough. However, where is it documented? Came up dry on google.
        --[[Joey]]
 
+       From <http://daringfireball.net/projects/markdown/syntax#html>:
+       > The only restrictions are that block-level HTML elements \97 e.g. &lt;div&gt;, &lt;table&gt;, &lt;pre&gt;, &lt;p&gt;, etc. \97 must be separated from surrounding content by blank lines, and the start and end tags of the block should not be indented with tabs or spaces. Markdown is smart enough not to add extra (unwanted) &lt;p&gt; tags around HTML block-level tags. [snip]
+       > Note that Markdown formatting syntax is not processed within block-level HTML tags. E.g., you can\92t use Markdown-style \*emphasis\* inside an HTML block.
+
+       Because [ [inlinepage] ] isn't separated by a blank line it gets treated as a block-level element. Hmm, will this stop all formatting, including *'s to em-tags? --[[JeroenSchot]]
+
+    Ah didn't realize you meant it fixed it at the markdown level. I'll think about making [[postprocessordirective]]s into preprocessordirectives instead, then I could use that fix (but I'm not sure how feasible it is to do that). By the way, I am considering adding a hack to prevent markdown's overzealous expansion of \_ and \* inside words. --[[Joey]]
+
 This page is now valid.
 Test: [validate this page](http://validator.w3.org/check?url=referer)