| Age | Commit message (Collapse) | Author |
|---|
|
Previously it broke in a few cases, e.g. with soft breaks.
This fixes the issue described in #578.
|
|
|
|
So we don't get `<h2.0>`.
|
|
* make_spec.lua: rename children to child
Naming a variable "children" when it holds one child is confusing, and blocks
naming actual children.
* make_spec.lua: fix migration of children nodes in create_anchors
Prior to this commit, when migrating the children of a node to a new one,
children are moved as they are iterated via `cmark_node_next`; however, when a
child is moved under the new node, its next relationship with its sibling is
broken, so in fact at most one child is migrated, and the rest are lost. This
resulted in cases like
[Decimal numeric character
references](@)
consist of...
(note the softbreak) being eventually rendered as
<a ...>Decimal numeric character</a>
consist of...
|
|
|
|
The format for the spec examples has changed from
.
markdown
.
html
.
to
```````````````````````````````` example
markdown
.
html
````````````````````````````````
One advantage of this is that `spec.txt` becomes a valid
Markdown file.
`tests/spec_test.py` has been changed to use the new format.
The old `tools/makespec.py` has been replaced by a lua
program, `tools/make_spec.lua`, which uses the `lcmark` rock
(and indirectly libcmark). It can generate
html, latex, and commonmark versions of the spec.
Pandoc is no longer needed for the latex/PDF version.
And, since the new program uses the cmark API and operates
directly on the parse tree, we avoid certain bad results we
got with the regex replacements done by the python script.
|
