Breaking a paragraph up, and aligning it
A paragraph broken into lines, then laid out four ways: left, right, centred, justified.
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.
The break keeps the character on the line it belongs to: the slash stays at the end of the upper line rather than opening the lower one. No hyphen is invented anywhere, so nothing is added to the text that was not written in it.
Nothing is left out and nothing is simplified: this is the program exactly as it runs, for the developer who uses this library. The third is the description itself: a plain list of what the page has to say, which is what the service is sent.
Read the Rust source Read the Python source Read the JSON source
The document is lighter than it was, and every page still looks exactly the same. See this document's row in the table of every example.
A paragraph broken into lines, then laid out four ways: left, right, centred, justified.
A word longer than the column that holds it: the library leaves it whole, or cuts it at the column's edge.
A justified column set twice: the long words breaking at their soft hyphens with a hyphen shown, or left whole, and a figure a no-break space keeps together.
A title, a rule, two paragraphs, a heading, a table of twenty-six rows and a footnote, handed over in reading order and broken across two pages by the engine.
One line of statuses set twice: in a company font alone, where the characters it has no glyph for come out as empty boxes, then with a second font behind it that draws them.
Four samples set twice each, once plain and once with a single setting activated: joined letters, small capitals, figures that hang below the line, and pairs moved closer together.