The Identity Card a Single Font Carries
Give one font of the document a packet of its own: the licence it is used under, its version, who made it.
Summary
A document says who wrote it and when; a font can say the same of itself. When a file has to prove, years later, that each face in it was used under the right licence, the answer is best kept on the font, not in a note somewhere else.
Technically
Written at the top level of a request, under
"font_metadata"
font_metadata writes an XMP /Metadata packet on the stream holding the font's program, never on the dictionaries that describe the font; a face the request draws itself carries it on its font dictionary. Each entry names the font it is for and carries a metadata of the two shapes page_metadata takes: facts, from which the packet is built, or packet, a packet already written. A font named twice carries the last packet given for it. A name no item draws with is refused, and so is a font whose program the file does not carry.
Request Schema
-
font_metadata— array, optional, empty by default. -
font_metadata[].font— string, required. The name items draw with the font by. -
font_metadata[].metadata— object, required. Eitherfacts, the fields the document's own card takes, orpacket, a packet already written and carried across unchanged.
Scope: the fonts named. metadata settles the document's own card and is not touched by this.
A Whole Request That Creates a PDF
One name below stands for a font file: put the encoded file in its place, or send the file itself beside the description, as a supplied part of the same call. One page carries a real font already encoded, and its request posts as it stands.
{
"version": "2.0",
"fonts": [{ "name": "body", "data": "PASTE_THE_FONT_FILE_BASE64_HERE" }],
"font_metadata": [
{
"font": "body",
"metadata": { "facts": { "title": "Body face, licensed for print and screen" } }
}
],
"items": [
{
"type": "text",
"rect": { "llx": 72, "lly": 700, "urx": 523, "ury": 740 },
"content": ["A face that says what it is"],
"font": "body",
"font_size": 12
}
]
}The document as a whole
The Numbers Reading Software Shows A Hundred Letters in a Single File What the Document Says about Itself What the Document Says about Itself, Said Once Text Nobody Can Copy The Notes a Program Leaves in the File for Itself The Notes a Program Leaves on One Page The Data a Program Hangs on a Run of Ink A File Still Readable Decades from Now The Print Standard the Document Claims The Variable Print Standard the Document Claims The Password That Opens It, and What May Be Done with It An Invoice a Person and a Machine Both Read The Address Relative Links Are Read Against The PDF Version the File Declares The Extensions to PDF the File Says It Uses What a Picture Says about Itself, and How It Is Read The Attachments the Document Carries Beside Its Pages Files the Document Names without Carrying The Attachments Shown as a Portfolio Which Attachments a Page Claims Which Attachments a Font Claims Which Attachments the Document's Card Claims A Document Card Written Elsewhere The Areas of a Page a Reader Measures In The Identity Card a Single Page Carries The Accessibility Standard the Document Claims The Standards the Finished Document Is Measured Against
Where to Go Next
Every JSON key of a request, in one page The other forty-one settings of a request