Age | Commit message (Collapse) | Author | Files | Lines |
|
* Use ctable package, which allows footnotes and
provides additional options.
* Made cell alignments work in multiline tables.
* Closes #272.
|
|
Closes #271.
|
|
|
|
|
|
Some EPUB e-readers, such as the Nook, require a meta element inside the
OPF metadata block to ensure the cover image is properly displayed.
When generating an EPUB using the `--epub-cover-image` option, this
patch adds the following meta element to the OPF metadata block in
`content.opf`:
<meta name="cover" content="cover-image" />
|
|
|
|
This prevents the code block from being interpreted as part of the list.
|
|
Otherwise LaTeX complains about \verb inside command argument.
Thanks to bbanier for reporting the bug.
|
|
Resolves Issue #304: problems with
(@item1; @item2)
because the final paren was being parsed as part of
the item key.
|
|
This reverts commit ec5410bc4e9d228b7dc0123061d80f9addf825bf.
|
|
This should make it easier to change the types later.
|
|
|
|
These previously caused infinite looping and stack overflows.
For example:
[^1]
[^1]: See [^1]
Note references are allowed in reST notes, so this isn't a full
implementation of reST. That can come later. For now we need to
prevent the stack overflows.
Partially resolves Issue #297.
|
|
This is also a cleaner way of inserting the slide divs.
Resolves Issue #296.
|
|
|
|
|
|
Instead of passing the epub cover image as a parameter, we now pass
it in the list of variables. This avoids the API change introduced
in f5cbb68534c52b292c57aaf741ab94442ddadd7a without losing the
new functionality.
|
|
|
|
CircleCode pointed out that the following markdown produces
out-of-order footnote markers in HTML:
-8<------------------------
some text^[with a footnote which will be #1]
issue
some other text^[with a footnote which will be #2]
-8<------------------------
This fixes the problem.
|
|
Thanks to Sivaram Gowkana for the patch.
|
|
So, in RST, 'http://google.com.' should be parsed as a link
to 'http://google.com' followed by a period.
The parser is smart enough to recognize balanced parentheses,
as often occur in wikipedia links: 'http://foo.bar/baz_(bam)'.
Also added ()s to RST specialChars, so '(http://google.com)'
will be parsed as a link in parens.
Added test cases.
Resolves Issue #291.
|
|
(Not just headers, as in the last patch.)
Patch from Andrea Rossato, slightly modified by JM.
|
|
API change: Added a parameter for the cover image path to
writeEPUB.
Followed best practices outlined in
http://blog.threepress.org/2009/11/20/best-practices-in-epub-cover-images/
|
|
The bug affected field lists with multi-line items at the
end of the list.
|
|
"First paragraph" as opposed to "Text body." This allows
users to specify e.g. that only paragraphs after the first
paragraph of a section are to be indented.
Thanks to Andrea Rossato for the patch.
Closes github Issue #20.
|
|
The point of the change is to allow html tags to be used freely
at the left margin of a markdown+lhs document.
Thanks to Conal Elliot for the suggestion.
|
|
This prevents "too many unprocessed floats." Resolves
Issue #285.
|
|
(This is still needed, even with recent base.)
Partially resolves Issue #286 (though now there is a
new markdown2pdf problem).
|
|
This reverts commit aec54899606bed2580394baa1369e58ede20fde8.
No need for this, since a UTF-8 charset will handle ascii just fine.
|
|
|
|
|
|
Currently supported only in HTML writer.
|
|
|
|
|
|
|
|
Previously, if you had formatting in the label of an Image
element, you'd get escaped HTML in the alt attribute. Now
you just get a plain string version, which seems preferable.
|
|
|
|
Removed blank lines. More consistent format.
|
|
|
|
|
|
Also removes any distinction between --no-wrap and default HTML
output.
Resolves Issue #134.
|
|
|
|
In normal form, Space elements only occur to separate two non-Space
elements. So, we never have [Space], or [, ..., Space].
|
|
|
|
The last patch did not handle cases with > 4 spaces.
Also added a more general test case.
|
|
The problem was in input like this:
[^1]: note
not in note.
Also added a test case for this.
|
|
|
|
This gives us proper line endings on windows, and some speed
improvements.
We fall back to the old functions if base < 4.2.
hGetContents is now exported.
|
|
Previously a file beginning " hi" would cause a parse error.
Also cleaned up comment parsing.
|
|
Previously pandoc got confused by blank rows in the header.
|