write_break_after.json
The JSON file of the “Break points after a slash or a hyphen” example. A justified column set twice: file paths and compounds running past the edge with no break points, then wrapping where a break after a slash or a hyphen is allowed.
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
Break only at spaces and a file path becomes one very long word. So does a hyphenated compound, and so does a part reference full of slashes — and those are exactly what a technical document is made of. A column that is comfortable for prose is far too narrow for them, and widening it to suit the worst one ruins the page for everything else.
What this example shows
- Break points allowed after a slash and after a hyphen.
- The breaking character kept at the end of the line it ends.
- Long paths wrapped without inventing a hyphen.