groff-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[groff] 12/18: groff_man_style(7): Add a FAQ about the ellipsis.


From: G. Branden Robinson
Subject: [groff] 12/18: groff_man_style(7): Add a FAQ about the ellipsis.
Date: Thu, 7 Apr 2022 01:29:27 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit 7fd8ced019d09eebc6a54661fa4c406014b7af55
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Thu Apr 7 12:30:24 2022 +1000

    groff_man_style(7): Add a FAQ about the ellipsis.
---
 tmac/groff_man.7.man.in | 67 +++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 67 insertions(+)

diff --git a/tmac/groff_man.7.man.in b/tmac/groff_man.7.man.in
index c0db3c24..e46a7629 100644
--- a/tmac/groff_man.7.man.in
+++ b/tmac/groff_man.7.man.in
@@ -3875,6 +3875,73 @@ _
 \fIanother-paragraph   \fIanother-paragraph
 _
 .TE
+.
+.
+.TP
+.\" Keep TWO spaces before that \c.
+\(bu Why doesn't the package provide a string to insert an ellipsis?  \c
+How do I make one?
+.
+Examples of ellipsis usage are shown above,
+in subsection \[lq]Command synopsis macros\[rq].
+.
+The idiomatic
+.I roff
+ellipsis is three dots (periods)
+with a \[lq]thin space\[rq] escape sequence
+.B \[rs]|
+internally separating them.
+.
+Since dots both begin control lines and are candidate end-of-sentence
+characters,
+however,
+it is sometimes necessary to prefix and/or suffix an ellipsis with the
+non-printing input break escape sequence
+.BR \[rs]& .
+.
+That fact stands even if a string is defined to contain the sequence;
+moreover,
+if the input breaks were included unconditionally as part of the string,
+end-of-sentence detection would be defeated in the event you used such a
+string at the end of an actual sentence.
+.
+(Ending a sentence thus is often poor style,
+but not always.)
+.
+A hypothetical string
+.B EL
+that contained an ellipsis,
+but not the trailing input break,
+would be interpolated when the trailing input break was needed.
+.
+Compare and contrast.
+.
+.RS
+.RS
+.EX
+Arguments are foo bar \[rs]*[EL]\[rs]& unless an option is given.
+Arguments are foo bar .\[rs]|.\[rs]|.\[rs]& unless an option is given.
+.EE
+.RE
+.
+By using a string,
+a whopping one character of typing has been saved,
+and even the presence of an ellipsis is obscured.
+.RE
+.
+.
+.IP
+Some fonts have an ellipsis character,
+and there is a Unicode character for it,
+but we discourage the use of these;
+they usually crowd the dots into a single character cell,
+and will not render at all if the output device doesn't have the glyph.
+.
+In syntax synopses,
+missing ellipses can cause great confusion.
+.
+Dots and space are universally supported.
+.\" XXX: Does an unconditional _preceding_ input break cause problems?
 _endif()dnl
 .
 .



reply via email to

[Prev in Thread] Current Thread [Next in Thread]