diff options
| author |   Ingo Schwarze <schwarze@openbsd.org> | 2013-12-26 17:23:42 +0000 |
|---|---|---|
| committer | Ingo Schwarze <schwarze@openbsd.org> | 2013-12-26 17:23:42 +0000 |
| commit | f6563ba0304acecf4e8cb3d3ca84faf6ebeac5d1 (patch) | |
| tree | 7fca2fbdd41537763a3d4374a2279749efee44ed /man_term.c | |
| parent | 2c58c78f1263202939348075128cbfaa56a7feb8 (diff) | |
| download | mandoc-f6563ba0304acecf4e8cb3d3ca84faf6ebeac5d1.tar.gz mandoc-f6563ba0304acecf4e8cb3d3ca84faf6ebeac5d1.tar.zst mandoc-f6563ba0304acecf4e8cb3d3ca84faf6ebeac5d1.zip | |
Rework the documentation of Spaces, using the Ossanna/Kernighan/Ritter
Heirloom Nroff/Troff User's Manual at the authoritative reference.
Part of our text was outright wrong.
Also, refrain from advertising the paddable non-breaking space `\~'
in the DESCRIPTION, for three reasons: For nroff mode, -Tascii, and
fixed width fonts in general, it makes no difference, so keep the
discussion simple. Compared to `\ ', '\~' is of questionable portability.
And if you want to keep words together, it is also more usual that you
don't want padding to intervene either.
Finally, drop the `\c' escape sequence (interrupt text processing)
which is not a special character but an input processing instruction
akin to the \<newline> escape sequence.
Diffstat (limited to 'man_term.c')
0 files changed, 0 insertions, 0 deletions