Last active
May 2, 2016 14:47
-
-
Save pdfkungfoo/c0132928421ebfdebcc13d8060fa55e2 to your computer and use it in GitHub Desktop.
Markdown source which exposes a "page overflowing" bug with Pandoc 1.17.0.2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
% Expertise on Topic Blah-Blah | |
% Someone, Sworn Expert Witness | |
% Some Day in Future | |
\newpage{} | |
This Markdown source file exposes a bug when using Pandoc to convert it to PDF: | |
it leads to an overflowing page. | |
The problem seems to be triggered by the fact that there are no text paragraphs (yet) in this document draft, only the outline of planned headings. | |
Command used: | |
pandoc -o out.pdf this.md --toc --number-sections | |
\newpage{} | |
# Backgrounds to this Expertise | |
# Procedural Methods to this Expertise | |
# Discoveries for this Expertise | |
## Claims of the Plaintiff | |
### "Plaintiff's Claim No. 1." | |
### "Plaintiff's Claim No. 2." | |
### "Plaintiff's Claim No. 3." | |
### "Plaintiff's Claim No. 4." | |
### "Plaintiff's Claim No. 5." | |
### "Plaintiff's Claim No. 6." | |
### "Plaintiff's Claim No. 7." | |
### "Plaintiff's Claim No. 8." | |
### "Plaintiff's Claim No. 9." | |
### "Plaintiff's Claim No. 10." | |
### "Plaintiff's Claim No. 11." | |
### "Plaintiff's Claim No. 12." | |
## Claims of the Defendant | |
### "Defendant's Claim No. 1." | |
### "Defendant's Claim No. 2." | |
### "Defendant's Claim No. 3." | |
### "Defendant's Claim No. 4." | |
### "Defendant's Claim No. 5." | |
### "Defendant's Claim No. 6." | |
### "Defendant's Claim No. 7." | |
### "Defendant's Claim No. 8." | |
### "Defendant's Claim No. 9." | |
### "Defendant's Claim No. 10." | |
### "Defendant's Claim No. 11." | |
### "Plaintiff's Claim No. 12." | |
# Expert's Statements in Relation to the Court's Evidence Order | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment