aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2018-08-08 14:16:08 +0000
committerIngo Schwarze <schwarze@openbsd.org>2018-08-08 14:16:08 +0000
commit5624285b18d5ee5185a1ba8c4ab8c7f2d64699f2 (patch)
tree3c4dc74f7c18ede4ef5f1da798fdbff28c71f912
parentaf289e8752b5a4f63e78b8c0ea70dc20f170004f (diff)
downloadmandoc-5624285b18d5ee5185a1ba8c4ab8c7f2d64699f2.tar.gz
mandoc-5624285b18d5ee5185a1ba8c4ab8c7f2d64699f2.tar.zst
mandoc-5624285b18d5ee5185a1ba8c4ab8c7f2d64699f2.zip
Reorder the text in the "Dashes and Hyphens" subsection to keep the
simplest and most important instructions together and at the beginning. No text change. Suggested by jmc@.
-rw-r--r--mandoc_char.750
1 files changed, 25 insertions, 25 deletions
diff --git a/mandoc_char.7 b/mandoc_char.7
index b4136418..bc17896c 100644
--- a/mandoc_char.7
+++ b/mandoc_char.7
@@ -1,4 +1,4 @@
-.\" $Id: mandoc_char.7,v 1.70 2018/08/08 14:03:27 schwarze Exp $
+.\" $Id: mandoc_char.7,v 1.71 2018/08/08 14:16:08 schwarze Exp $
.\"
.\" Copyright (c) 2003 Jason McIntyre <jmc@openbsd.org>
.\" Copyright (c) 2009, 2010, 2011 Kristaps Dzonsons <kristaps@bsd.lv>
@@ -76,30 +76,6 @@ blue-eyed
lorry-driver
.Ed
.Pp
-If a word on a text input line contains a hyphen, a formatter may decide
-to insert an output line break after the hyphen if that helps filling
-the current output line, but the whole word would overflow the line.
-If it is important that the word is not broken across lines in this
-way, a zero-width space
-.Pq Sq \e&
-can be inserted before or after the hyphen.
-While
-.Xr mandoc 1
-never breaks the output line after hyphens adjacent to a zero-width
-space, after any of the other dash- or hyphen-like characters
-represented by escape sequences, or after hyphens inside words in
-macro arguments, other software may not respect these rules and may
-break the line even in such cases.
-.Pp
-Some
-.Xr roff 7
-implementations contains dictionaries allowing to break the line
-at syllable boundaries even inside words that contain no hyphens.
-Such automatic hyphenation is not supported by
-.Xr mandoc 1 ,
-which only breaks the line at whitespace, and inside words only
-after existing hyphens.
-.Pp
The en-dash is used to separate the two elements of a range,
or can be used the same way as an em-dash.
It should be written as
@@ -135,6 +111,30 @@ But currently, no practically relevant manual page formatter actually
requires that subtlety, so in manual pages just write plain
.Sq -
to represent hyphen, minus, and hyphen-minus.
+.Pp
+If a word on a text input line contains a hyphen, a formatter may decide
+to insert an output line break after the hyphen if that helps filling
+the current output line, but the whole word would overflow the line.
+If it is important that the word is not broken across lines in this
+way, a zero-width space
+.Pq Sq \e&
+can be inserted before or after the hyphen.
+While
+.Xr mandoc 1
+never breaks the output line after hyphens adjacent to a zero-width
+space, after any of the other dash- or hyphen-like characters
+represented by escape sequences, or after hyphens inside words in
+macro arguments, other software may not respect these rules and may
+break the line even in such cases.
+.Pp
+Some
+.Xr roff 7
+implementations contains dictionaries allowing to break the line
+at syllable boundaries even inside words that contain no hyphens.
+Such automatic hyphenation is not supported by
+.Xr mandoc 1 ,
+which only breaks the line at whitespace, and inside words only
+after existing hyphens.
.Ss Spaces
To separate words in normal text, for indenting and alignment
in literal context, and when none of the following special cases apply,