This change is more invasive and difficult for me as not all existing
preprocessor directives directly translate to `if () {}`.
Instead of passing `--with-fenced-code` to `configure.sh`, now use
`MKD_FENCEDCODE` or `-ffencedcode`.
The output of `markdown -VV` will now display `FENCEDCODE` if the
feature is enabled and `!FENCEDCODE` if it is disabled rather than
displaying `FENCED-CODE` if the feature is enabled.
The following syntax should now be valid:
```lang
CODE HERE
```
And generates:
<pre><code class="lang">CODE HERE
</code></pre>
This syntax allows support for GitHub Flavored Markdown style
fenced code blocks used on [GitHub][1].
[1]: https://help.github.com/articles/github-flavored-markdown
which gives me the ability to do verbose and nonverbose test
suite running (`VERBOSE=1 make test` is the traditional output
now, and `make test` just gives pass/fail on each .t file)
1. Officially expose mkd_compile(), mkd_cleanup(),
mkd_generatehtml().
2. Internally use the new Document structure, which
hold the markup and (optionally) header information.
3. Support ``--enable-<foo>`` during configure.sh
* change --with-dl-tag to --enable-dl-tag.
* add --enable-pandoc-header to support pandoc headers.