summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-01-05 01:47:57 -0500
committerJoey Hess <joey@kodama.kitenet.net>2008-01-05 01:47:57 -0500
commite0901334c9bc2e29beca63dd4ddcade59c83af34 (patch)
tree1594e76d1268f33658ba514150d0898e9303851d /doc
parent1fb1d6c1830a3d80bd6940bc2b24ca4f673e1bed (diff)
response
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/undefined_tags_or_mismatched_tags_won__39__t_get_converted.mdwn12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/undefined_tags_or_mismatched_tags_won__39__t_get_converted.mdwn b/doc/bugs/undefined_tags_or_mismatched_tags_won__39__t_get_converted.mdwn
index 9463cfb1b..13ebe1cab 100644
--- a/doc/bugs/undefined_tags_or_mismatched_tags_won__39__t_get_converted.mdwn
+++ b/doc/bugs/undefined_tags_or_mismatched_tags_won__39__t_get_converted.mdwn
@@ -32,3 +32,15 @@ The out put is:
</div>
<p></div></p>
+
+> This is a bug in markdown. Actually, not converting `<` and `>` in tags is a
+> markdown feature -- markdown allows inserting arbirary html, even if it's
+> made-up tags. And putting paragraph tags around your `<section>` tag is
+> understandable, since markdown can't know if `<section>` is intended to
+> be a block-level tag or not. The bug is that it puts the `<p>` around the
+> trailing `<div>` -- it does know what a div is, and it should know that's
+> illegal and not do it. I've filed a [bug report](http://bugs.debian.org/459269) about that issue
+> alone. If you feel the other things you brought up are bugs, please talk
+> to the markdown maintainer. --[[Joey]]
+
+[[tag done]]