Adding fenced div blocks to markdown reader

[mpickering]

This is speculative - I want to move discussion forward by having something concrete to talk about.

Closes #168

[ousia]

@mpickering, many thanks for this. It looks really awesome.

Contributing to the discussion (although I’m not sure whether this is the best place to do it): would it be possible to have also fenced spans (such as in ^span^{.class #identifier lang="grc"}?

[bpj]

EDIT: I just noticed that I said much the same over at #168 about a month ago...
Anyway I actually feel strongly about this, strange as it may seem!

@mpickering: please note what @jgm said at #168 (comment). I don't think 'uparrow' makes very much sense in this context.
Note that we already have ^superscript^ and I think ^^smallcaps^^ would be nice, the 'uparrows' being iconic for 'kind of uppercase'.
(Also it so happens that since they are 'accents' all of ~ ^are shift/altgr deadkeys on my Swedish keyboard, so I must hold down shift/altgr and hit one of those keys six times to get three of those characters For some odd reason hitting the same key more than three or four times in a row is annoying. :-) So I for one would be very grateful for:::instead of^^^! I would be even more grateful if you implement [span text]{ATTRIBUTES}as well (and^^smallcaps^^` if I dare ask! :-).

[ousia]

@mpickering, I agree with both proposals from @bpj: [span]{.class #identifier lang="grc"} and ^^small caps^^.

In that case, a more consistent syntax for fenced blocks would be:

[[[ {.warning #fenced-block-1}
This is a fenced div block.

With multiple pagragraphs.
]]]

Using different starting and closing characters makes nesting easier for the end user (so that indentation isn’t mandatory for nesting).

[tarleb]

Superseded by fda0c01.