Would you please consider moving some of this to a personal blog or at
least phrase your argument differently?
+1 !
--
Már
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
The list numbering behavior is documented, so it's not a bug;
Absolutely correct - it is broken by design.
What I meant to say was that from a naïve user's (writer's) point of
view, it's a bug.
Changing this behaviour in Markdown would obviously cause sloppy
list-numbering to appear here and
if the author of the baseline spec spoke up and
said that the current behavior is a bug, not a
design feature.
I thought it was already established that Gruber is not interested in
taking the development of Markdown any further - to such extent that
he doesn't even release publicly his
major change to fix something that only very
rarely occurs.
This has happened to me a few times.
I've however learned to work around it by adding empty HTML comments,
or some such.
I guess less tech-savy users insert a single period or a dash.
I've also often been irritated by the limitation
Aristotle Pagaltzis [EMAIL PROTECTED] wrote:
What about setting value on each li instead?
Equally deprecated.
The HTML spec authors have admitted that they believe this particular
change was a mistake on their behalf.
All browsers support the value attribute on ol lis, and there are
This problem has caused me grief more than once...
I've been forced to add a paragraph of full-stops to break up the
`blockquote`s - like this:
Some cool quote
...
Some other cool quote
This feels like a bug in Markdown to me.
--
Már
