An invoice laid on a letterhead
An invoice laid on a letterhead somebody else made.
A form that is also a PDF/A-3 file: every field already drawn, with a visible frame, expecting nothing from the reader's software.
A form and an archival file pull in opposite directions. A form leaves its fields for the reader's software to draw; an archival file forbids exactly that and demands that everything already be drawn into the page. This example brings the two together.
Each field carries its own drawing — the typed value drawn letter by letter, a tick or a dot drawn line by line — so the file expects nothing from the reader's software and needs no font it does not already carry. Every field has a frame around it so it is plain where to click, and the page says so; the frames stay optional, and the same form is valid without them.
The same document is written twice, once in each language. Both files are shown in full, with the code coloured on the server, and can be copied in one click.
The same document is written in each of these languages. Open the one you want to look at.
| Before | 120,803 bytes |
|---|---|
| Now | 50,301 bytes |
| Saved | 58.4 % |
Not one mark on the page changed. See every document measured.
An invoice laid on a letterhead somebody else made.
A supply agreement standing on three PDF files the customer sent: a headed sheet under the front page, a plain sheet under every page the schedule runs to, and a page of conditions that goes in whole.
What an unlicensed copy looks like: the evaluation watermark the library stamps on every page.
A form a reader fills in: text boxes, a check box, a drop-down, radio buttons.
An electronic invoice: a PDF/A-3 file carrying its own XML.
The ICC profile the library embeds in a PDF/A file.