write_aztec.json
The JSON file of the “Aztec codes” example. The code on rail and airline tickets, and the reason is room: it needs no band of white around it, which is the first thing trimmed off a layout that has run tight.
This file is a request: an application sends it over the network to the server, which creates the PDF and sends it back. It makes the same page as the Rust and Python versions of this example. A request names every file it uses, never its content; the call carries the request and the files together. A font the server already holds, such as DejaVuSans, is named with nothing attached. Send the request to the address the API page gives.
What this example is for
Aztec is the code on rail and airline tickets in Europe, and the reason is room. Every other two-dimensional code demands a band of white all the way round it, which on a ticket the size of a bus pass is room nobody has — and that margin is the first thing somebody trims off when the layout gets tight, quietly breaking the code.
What this example shows
- Aztec codes drawn line by line, square by square.
- A code that sits hard against anything, thanks to the rings at its centre.
- Three codes at three strengths of protection, biggest where it is highest.