Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
A tag must start with `<` followed by `!`,`?`, `/`, or a letter.
This makes it more useful in the wikimedia and markdown parsers.
|
|
|
|
|
|
|
|
|
|
They only work on headers, because pandoc forces same
alignment for all cells in a column.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Including word-ending links and the "pipe trick."
|
|
|
|
|
|
|
|
|
|
Also check for column 1 in preformatted text.
|
|
They can be postprocessed with a pandoc script.
|
|
Parse one tag, then use a case statement.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For example:
# one
# two
### skip!
### skip
|
|
|
|
|
|
Text.Pandoc.Readers.MediaWiki module,
tests/mediawiki-reader.{txt,native}.
|
|
|
|
Now it should tell you that it was looking for \end{env},
instead of giving "unknown parse error."
|
|
|
|
Removed these from list of inline commands.
|
|
|
|
|
|
Closes #555.
|
|
Closes #604.
|
|
|