fnt/source-sans-3.css


@font-face {
  font-family: 'Source Sans 3';
  font-style: normal;
  font-weight: 400;
  src: url('source-sans-3/Regular.ttf') format('truetype');
}

@font-face {
  font-family: 'Source Sans 3';
  font-style: normal;
  font-weight: 700;
  src: url('source-sans-3/Bold.ttf') format('truetype');
}

@font-face {
  font-family: 'Source Sans 3';
  font-style: italic;
  font-weight: 400;
  src: url('source-sans-3/Italic.ttf') format('truetype');
}

@font-face {
  font-family: 'Source Sans 3';
  font-style: italic;
  font-weight: 700;
  src: url('source-sans-3/BoldItalic.ttf') format('truetype');
}
Markdown to PDF: the mdpdf command, and the fonts it needs This snapshot carries sks/tns/, the translation directory, into the distribution for the first time, together with the two default font families its stylesheet names. sks/tns/ holds two converters in opposite directions. md_to_sks.py converts Markdown to Klammertext, recording what it cannot convert exactly as "#[MD ... ]#" markers so a draft carries its own worklist. md_to_pdf.py renders Markdown straight to PDF through a headless Chromium driven over the DevTools Protocol, bypassing Klammertext entirely -- the route for a document that is not ready to convert, and a permanent one for Markdown that Klammertext cannot represent well. Neither is loaded by the SKS; md_to_pdf needs markdown-it-py, which it keeps in a virtual environment of its own and creates with --setup. The everyday form of the second is the mdpdf command, a shell function in sks/tns/mdpdf.sh that env/runtime.env sources, so anyone with the Klammertext environment has it: mdpdf notes.md # writes notes.pdf beside it It supplies the house fonts, the size matching, and the code wrapping, completes on .md at the TAB key, and takes its defaults from MDPDF_ variables so one can be changed in a shell profile without copying the function. It is POSIX shell rather than zsh, since runtime.env is sourced from bash profiles too. Two things the stylesheet does that a print stylesheet usually cannot. Code lines are wrapped to a column count MEASURED from the rendered page rather than written down -- the browser is asked how many characters a code box holds, over every box in the document, so the wrapping stays right when the fonts, sizes or margins change. And the page number is a CSS Paged Media margin box, which current Chromium implements, so it is set in the document's own face instead of the browser's generic sans. fnt/ gains EB Garamond and Source Sans 3, the serif and sans the stylesheet asks for by default. (from dev 97d4f244c737) 2026-08-09 15:54:05 +02:00
			`@font-face {`
			`font-family: 'Source Sans 3';`
			`font-style: normal;`
			`font-weight: 400;`
			`src: url('source-sans-3/Regular.ttf') format('truetype');`
			`}`

			`@font-face {`
			`font-family: 'Source Sans 3';`
			`font-style: normal;`
			`font-weight: 700;`
			`src: url('source-sans-3/Bold.ttf') format('truetype');`
			`}`

			`@font-face {`
			`font-family: 'Source Sans 3';`
			`font-style: italic;`
			`font-weight: 400;`
			`src: url('source-sans-3/Italic.ttf') format('truetype');`
			`}`

			`@font-face {`
			`font-family: 'Source Sans 3';`
			`font-style: italic;`
			`font-weight: 700;`
			`src: url('source-sans-3/BoldItalic.ttf') format('truetype');`
			`}`