diff options
| -rw-r--r-- | doc/bugs/undefined_tags_or_mismatched_tags_won__39__t_get_converted.mdwn | 12 |
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]] |