Fonts and their rights
Fonts are licensed. Paprika records, for every font it renders with, what its licence allows: showing it in the editor, using it on the server, embedding it in PDFs and redistributing it in packages. The server trusts only rights recorded with the font (in your organisation’s font library, or in the published template), never what a request says.
What it means for renders
Section titled “What it means for renders”- Laying out a document needs the server right; making a PDF needs the embedding right too.
- Rights are checked as they are now, at every render. A right taken away stops renders at once.
- A render that a font’s rights don’t allow is refused before any layout, 422
font-rights, naming the font and the right. No policy renders past it. - A version published with a font that may not be embedded carries the warning
font-not-embeddable: it lays out and makes images, but no PDF.
The font library
Section titled “The font library”Your organisation’s library holds the bundled fonts, whose rights are verified, and fonts uploaded by your designers, with the rights they confirmed for them and who confirmed them. List it to see what renders may use:
curl -H "Authorization: Bearer $PAPRIKA_KEY" "$PAPRIKA_URL/v1/fonts"Uploading fonts and confirming their rights is usually done in the editor (Settings → Fonts…); the fonts operations do the same through the API, with the publish scope.