Pages that link out of themselves and to each other.
A link draws nothing, so nothing on a page proves it is there: only following it does. This document is built to be followed — the first page carries a contents list whose lines lead to the pages after it and an address that leaves the document altogether, and every later page leads back.
Bookmarks are here too, so the same structure appears down the side of the reader. The example also runs in an archival mode, because a link in a PDF/A file obeys rules of its own about what it may point at and how it must be described.
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 | 112,095 bytes |
|---|---|
| Now | 41,491 bytes |
| Saved | 63.0 % |
Not one mark on the page changed. See every document measured.
Thirteen slides, each stating the effect it arrives by — all twelve the standard defines — how long that effect takes and how long the slide stands before the next one comes. The file opens full screen, which is the only place a reader reads any of it.
Four pages that state what happens the moment the file is opened: which page it opens on and how much of the window that page fills, the bookmarks shown beside it, the pages two at a time, a print dialogue already filled in, and the address its relative links are read against.
Links and marks hung on text the engine has already placed: a band behind a line, an underline, a boxed cell — every rectangle taken from what the layout and the table report afterwards, none of it measured by hand.
Pages numbered by their labels rather than their position.
A page of Data Matrix codes, drawn as squares.
A page of PDF417 codes, drawn as stacked bars.