Markdown to PDF

Markdown is plain text with structural intent, and honouring that intent is what separates this from TXT to PDF. The file is parsed into a document tree first — headings, paragraphs, ordered and unordered lists with their nesting, fenced code blocks, block quotes, inline emphasis and strong text, and link text — and only then typeset. Each node type gets its own treatment: heading levels are sized proportionally from your base font size and given space above and below, list items are indented per nesting level with their markers drawn, fenced and indented code use Courier by default or the regular body font when Monospaced code blocks is off, and block quotes are inset. Code spaces are retained, tabs expand to four spaces, and overlong code lines are truncated with ... rather than wrapped; proportional code cannot guarantee column alignment. Emphasis maps to the bold and italic variants of the standard font families, which is why inline formatting survives rather than leaking through as literal asterisks. Pagination is content-aware enough to avoid orphaning a heading at the foot of a page. As with plain text the output is real embedded text, so the PDF is searchable and small, and the whole parse-and-typeset pass happens locally.