> Yup, thats why. Although quotes are acceptable as well. The only way > to do the encoding of spaces is to always require quotes around the > title text. A quick look at the syntax rules indicates that quotes > should always be required and I could change python-markdown's
I would say that a brief look at "Markdown Syntax" indicates that as a spec it's wildly underdefined and this is just one of the many things that aren't spelled out. Considering the examples, the argument that titles should always have quotes is just as plausible as the argument that URLs should never have spaces. Considering this, my intuition would be to stick with what we've got. It would be great if we had some sort of framework for evolving the standard. Then it would make sense to discuss this issue, settle on what the behavior _should_ be and request that all implementations try to conform to it. But unfortunately we don't. So, when one implementation does one thing and another does another, one can't really meaningfully ask which one is right and which is wrong. > it. Perhaps the other python-markdown dev would feel different. I guess we agree on the bottom-line even if our quick readings of "Markdown Syntax" differ. :) - yuri _______________________________________________ Markdown-Discuss mailing list [email protected] http://six.pairlist.net/mailman/listinfo/markdown-discuss
