Skip to content

Commit

Permalink
Use \*(GR in a few places in the body text.
Browse files Browse the repository at this point in the history
One of them was not italicized.  The others produce the same output.
This change doesn't touch "groff" in section headers where it's set in
bold italic or where all the header is already set in italic.
  • Loading branch information
nbuwe committed Apr 4, 2021
1 parent 5fdeb11 commit 5bc0928
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions doc/troff/doc.tr
Original file line number Diff line number Diff line change
Expand Up @@ -6993,7 +6993,7 @@ to the \fB&C\fR and \fB&g\fR registers.
Nevertheless it is not recommend to do so
without reason.
For instance macro packages read \fB\en(.g\fR to test
if they are processed with groff.
if they are processed with \*[GR.]
Setting \fB&g\fR to \fB1\fR with the \fB&nr\fR request
also has some side effects in Heirloom \*(TR:
.de ListBegin
Expand All @@ -7013,7 +7013,7 @@ also has some side effects in Heirloom \*(TR:
.ListBegin
.tr &&
.ListItem
\fIgroff\fR\^'s notation for accessing symbols with
\*(GR\^'s notation for accessing symbols with
\fB\e[char\fIn\fB]\fR and \fB\e[u\fIXXXX\fB]\fR
are enabled.
.ListItem
Expand All @@ -7033,7 +7033,7 @@ leads to a different placement of the middle title element
with \*(NR under certain conditions.
This is emulated by setting \fB.g\fR to 1.
.ListItem
\fIgroff\fR\^'s left italic correction escape \fB\e,\fR is removed
\*(GR\^'s left italic correction escape \fB\e,\fR is removed
from the input instead of producing a \(oq\fB,\fR\(cq.
.ListEnd
.tr &.
Expand Down

0 comments on commit 5bc0928

Please sign in to comment.