Proper parsing of codeblocks in generated documentation

[Chris Watson]

Currently code blocks just get left as is, it would be nice to have them parse properly. An example is this:

|[<!-- language="C" --> enum {

PROP_0,
PROP_FOO,
PROP_LAST

}; ]|

It should be possible to get the parser to recognize these blocks and swap them out for proper markdown blocks.