Jacques Distler

But ~~~~~ \begin{c} \label{DoubleNegationMonad} \end{d} \begin{proof} Immediate from \ref{Monads} ~~~~~ works [just fine](https://johnmacfarlane.net/babelmark2/?normalize=1&text=%5Cbegin%7Bc%7D%0A%5Clabel%7BDoubleNegationMonad%7D%0A%5Cend%7Bd%7D%0A%5Cbegin%7Bproof%7D%0AImmediate+from+%5Cref%7BMonads%7D), as [does](https://johnmacfarlane.net/babelmark2/?normalize=1&text=%5Cbegin%7Bc%7D%5Clabel%7BDoubleNegationMona%7D%0A%5Cend%7Bd%7D%0A%5Cbegin%7Bproof%7D%0AImmediate+from+%5Cref%7BMonads%7D) ~~~~~ \begin{c}\label{DoubleNegationMona} \end{d} \begin{proof} Immediate from \ref{Monads} ~~~~~ Curious. Trivial to "fix", but I don't...

"Fixed" in 97c0489.

Alternatively, one can [fix `CharSourceStrscan`](https://github.com/distler/maruku/commit/8dd8c22d6c3b9ee15410483365c9b505abdf6d5e) to be multi-byte-aware. I would still make `CharSourceManual` the default, 'cuz [it's faster](https://github.com/distler/maruku/commit/dd76daf3bf25dbf014fb4e5de15cde05d176c60f).

If there's interest in a multi-byte-aware version, I can make a pull request out of the above-linked commits.

> I don't know if it worked differently in 0.6 or if it's just that spans where not being parsed for markdown before. See the resolution to [Issue 31](https://github.com/bhollis/maruku/issues/31).

If the input says ``, Nokogiri serializes this to ``. Which is perfectly equivalent, when interpreted as XHTM, but means something radically different (an opening `div` tag, with no corresponding...

Correct. The extension is not enabled here. It is, in my Nokogiri branch.

I don't know how to do that from Rubgems, but Bundler [handles that task just fine](http://gembundler.com/git.html).

I believe that you need at least five '~'s to signal the start of a fenced codeblock, and an equal (or larger) number to end one.

Extra dependencies? Y'mean Nokogiri?