diff options
author | Ingo Schwarze <schwarze@openbsd.org> | 2015-09-02 15:38:35 +0000 |
---|---|---|
committer | Ingo Schwarze <schwarze@openbsd.org> | 2015-09-02 15:38:35 +0000 |
commit | 1bca1b26aa408603e89d1a896729319ba8f93084 (patch) | |
tree | 5ca52cff40e77122e55e646716e8183ba39e2aec /preconv.c | |
parent | dfd27e6cd9c8f1f55ef0e659bcb6dd71d22a1057 (diff) | |
download | mandoc-1bca1b26aa408603e89d1a896729319ba8f93084.tar.gz |
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 'preconv.c')
0 files changed, 0 insertions, 0 deletions