write_flow_break.json
The JSON file of the “Breaking an overlong word” example. A word longer than the column that holds it: the library leaves it whole, or cuts it at the column's edge.
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
This example sets the same paragraph twice in a column too narrow for one of its words: every layout eventually meets the word that will not fit — a chemical name, a German compound, a web address, an order reference nobody thought about. The word turns up in production, in one record out of a thousand, long after the team signed the layout off, and it comes back with the next reference, whatever width the column is given. The overlong setting decides: overflow leaves the whole word to run past the edge, break cuts it after the last glyph that fits.
What this example shows
- The same paragraph running past the edge of the column, then kept inside it.
- The two settings one above the other on the same page of the PDF.
- The same choice on a block of text, on a table cell and on text that changes style part-way; this example shows only the block of text.