massifrg

I'm going to encode `Space` and `Str` xml elements this way: - `` is a single space, multiple spaces can be specified as ``, so `` is equivalent to ``...

> I'm going to encode `Space` and `Str` xml elements this way: > > * `` is a single space, multiple spaces can be specified as ``, so `` is...

I learnt how to make a benchmark, with ```sh cabal bench ``` or ```sh cabal bench --benchmark-options="-p xml" ``` The writer benchmarks are encouraging, because `xml` is faster than any...

> I would guess that the XML representations are also considerably more compact than the JSON ones (because of the implicit representation of String, Space sequences). ```sh $ pandoc -f...

I changed some attributes of the XML format for better consistency with Pandoc types definition: - `Image` `src` is now `url` - `Link` `href` is now `url` - `Cell` `rowspan`...

I renamed the Target url of Image and Link back to "src" and "href" respectively. The documentation says "url", but it's not the name of a haskell type or constructor,...

> You can always rebase this draft PR so that it has the structure of commits (and messages) that you like. I made a first rebase to shorten the history...

I realized that my rebase efforts produced some mess, because in my "xml" branch I periodically merged the main branch. The process of re-basing forced me to solve conflicts on...

> I would make a copy of this branch how it is (in case you need to go back to it), then fix the rebasing here. It shouldn't be too...

Today I synced my pandoc repository and tried to merge (locally) the "xml" branch into "main" with success. I'm afraid there's still the problem of commit messages' length, that I...