| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Except were "short names" are explained in the docs, all references
to the buitlin extensions now use `markdown.extensions.*` in
anticipation of #336.
|
| |
|
| |
|
|
|
|
|
|
| |
Simplified, unified style, added some undocumented options.
NOTE: Footnotes/UNIQUE_IDS stays mostly undocumented
|
|
|
| |
Must remember to spellcheck everything I type.
|
|
|
| |
This addresses a misunderstanding reported in issue #273. The behavior has not changed. The docs just better reflect the actual behavior better. Apparently using the word "definition" both for footnotes and definition lists was an unfortunate coincidence that created confusion. We now use the term "footnote content".
|
|
|
|
|
|
|
|
|
| |
The documentation uses features of Python-Markdown that are not supported on
GitHub and it's better to get a source view of the docs anyway. For example,
that way comments and bug reports can reference a specific line of a file.
Of course, it makes sense for Github to render the README, so that is left
with the `.md` file extension.
|
| |
|
|
Still need to do non-extra extensions.
|