diff options
author | Alejandro Colomar <alx@nginx.com> | 2023-04-26 15:29:00 +0200 |
---|---|---|
committer | Alejandro Colomar <alx@nginx.com> | 2023-05-08 17:47:28 +0200 |
commit | 7fdd5b035f3b22f1424115c9b31ad675ee1619aa (patch) | |
tree | 81810f4daa5c3b1c48f0e6dea3622d673601de86 /test/test_go_application.py | |
parent | 147ee8abd650c373cb1022dad2a9a0b8522aea8b (diff) | |
download | unit-7fdd5b035f3b22f1424115c9b31ad675ee1619aa.tar.gz unit-7fdd5b035f3b22f1424115c9b31ad675ee1619aa.tar.bz2 |
Docs: not using shouty caps in unitd.8.
There was a recent unanimous agreement by maintainers of groff, mandoc,
the Linux man-pages, and other relevant programmers, that manual pages
should not use uppercase unnecessarily. Use of uppercase in the title
and in the section's titles dates from before one could use bold,
italics, and other such formatting, so that it was the way of giving
more importance to certain parts of a page. Nowadays, we use bold, so
uppercase is unnecessary.
Moreover, using uppercase in the title is bad, since it removes
information. If we keep the exact casing used in the program (or
function) name, we provide more information. And anyway, if users want
to read in uppercase, they can program certain mdoc(7) or man(7) macros
to transform their arguments into uppercase. This could be done via
</etc/groff/mdoc.local> and </etc/groff/man.local>.
There's a plan of transforming OpenBSD pages and the Linux man-pages to
stop using uppercase. Other projects may join. That will likely happen
in the following months. Let's align with this.
Reviewed-by: Artem Konev <a.konev@f5.com>
Signed-off-by: Alejandro Colomar <alx@nginx.com>
Diffstat (limited to 'test/test_go_application.py')
0 files changed, 0 insertions, 0 deletions