John MacFarlane

Tables not supported for gfm output

3

Line 484 of CMarkGFM.hsc: ```haskell TABLE aligns -> error "constructing table not supported" TABLE_ROW -> error "constructing table row not supported" TABLE_CELL -> error "constructing table cell not supported" ```...

`decodeImageWithMetadata` returns the following metadata for [this image](https://github.com/ksesong/pandoc-image-fitting/raw/master/test-3.jpg) (see jgm/pandoc#6936). ``` ,Width :=> 4608 ,Height :=> 3456 ,Exif (TagUnknown 40963) :=> ExifLong 2539 ,Exif (TagUnknown 40962) :=> ExifLong 4537 ```...

Instead of a list of [FormattingSpec], let's have a FormattingSpecMap. Define Monoid for this so that if you have two formatting specs for the same character, one a single-matcher and...

Implement `citations` extension

2

As in pandoc: https://pandoc.org/MANUAL.html#extension-citations Implement in commonmark-core, commonmark-cli, commonmark-pandoc. This is tricky: we need to make sure this comes first in bracketed specs to avoid interpretation as a span.

Improve performance

4

See notes on performance in the README.md.

Make source positions a parser option?

5

Instead of handling it with typeclasses. This would allow simpler typeclasses: Html, Pandoc. It might also allow us to improve performance by avoiding the work of storing and computing ranges.

For example, for duplicate link references.

Implement `implicit_figures` extension

1

As in pandoc: see https://pandoc.org/MANUAL.html#extension-implicit_figures Implement in commonmark-core, commonmark-cli, commonmark-pandoc.

New pathological parsing for fenced divs

1

``` python -c 'n=800; print("::: {#id}\n" * n + "a\n" + ":::\n" * n)' ``` This is a problem with the new fix for detecting fence closers. At each close...

The current system (defining a new typeclass instance for the constructors) doesn't give fine-grained enough information (e.g. it doesn't distinguish code span delimiters from the code). And it is awkwardly...