aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/man.c
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2015-09-02 15:38:35 +0000
committerIngo Schwarze <schwarze@openbsd.org>2015-09-02 15:38:35 +0000
commitceb333844fd9e76e1de9bcbdba748f57bc603591 (patch)
tree9b97c8598b7fe695f12f8266d60fd6d722304385 /man.c
parent1b0bdf49f16badf24d9b0c44bb5228bcafde6fe4 (diff)
downloadmandoc-ceb333844fd9e76e1de9bcbdba748f57bc603591.tar.gz
mandoc-ceb333844fd9e76e1de9bcbdba748f57bc603591.tar.zst
mandoc-ceb333844fd9e76e1de9bcbdba748f57bc603591.zip
Recommend an unambiguous escape for minus signs instead of \-.
Historically, \- was used in troff for three cases: flags/pathnames, en dashes, and minus signs. mandoc_char(7) currently recommends it for minus signs, recommends \(en for en dashes, and doesn't mention flags/pathnames. In the old days, nroff rendered \- as ASCII '-', and troff rendered it as en dash/minus (which were visually indistinguishable). In Unicode, en dashes and minus signs are semantically distinct and encoded differently (U+2013 for en dash, U+2212 for minus), and often rendered differently too. Meanwhile ASCII '-' has been renamed "hyphen-minus" and fonts typically render it closest to a hyphen, not a minus. There is very little consistency across roff implementations and output formats for what Unicode character \- corresponds to. So at least for minus signs, change the recommendation to the unambiguous \(mi escape. from bentley@, ok jmc@ (after reams of discussion)
Diffstat (limited to 'man.c')
0 files changed, 0 insertions, 0 deletions