Manpages

GROFF

NAME

DESCRIPTION

This document gives only short descriptions of the predefined roff language elements as used in groff. Both the classical features and the groff extensions are provided.

Historically, the roff language was called troff. groff is compatible with the classical system and provides proper extensions. So in GNU, the terms roff, troff, and groff language could be used as synonyms. However troff slightly tends to refer more to the classical aspects, whereas groff emphasizes the GNU extensions, and roff is the general term for the language.

This file is only a short version of the complete documentation that is found in the groff info(1) file, which contains more detailed, actual, and concise information.

The general syntax for writing groff documents is relatively easy, but writing extensions to the roff language can be a bit harder.

The roff language is line-oriented. There are only two kinds of lines, control lines and text lines. The control lines start with a control character, by default a period or a single quote all other lines are text lines.

Control lines represent commands, optionally with arguments. They have the following syntax. The leading control character can be followed by a command name; arguments, if any, are separated by blanks from the command name and among themselves, for example,

.command_name arg1 arg2

For indentation, any number of space or tab characters can be inserted between the leading control character and the command name, but the control character must be on the first position of the line.

Text lines represent the parts that will be printed. They can be modified by escape sequences, which are recognized by a leading backslash These are in-line or even in-word formatting elements or functions. Some of these take arguments separated by single quotes others are regulated by a length encoding introduced by an open parenthesis or enclosed in brackets and

The roff language provides flexible instruments for writing language extension, such as macros. When interpreting macro definitions, the roff system enters a special operating mode, called the copy mode.

The copy mode behavior can be quite tricky, but there are some rules that ensure a safe usage.

1.

Printable backslashes must be denoted as To be more precise, represents the current escape character. To get a backslash glyph, use

2.

Double all backslashes.

3.

Begin all text lines with the special non-spacing character

This does not produce the most efficient code, but it should work as a first measure. For better strategies, see the groff info file and groff_tmac(5).

Reading roff source files is easier, just reduce all double backslashes to a single one in all macro definitions.  

GROFF ELEMENTS

There are two kinds of roff commands, possibly with arguments. Requests are written on a line of their own starting with a dot or a whereas Escape sequences are in-line functions and in-word formatting elements starting with a backslash

The user can define her own formatting commands using the request. These commands are called macros, but they are used exactly like requests. Macro packages are pre-defined sets of macros written in the groff language. A user's possibilities to create escape sequences herself is very limited, only special characters can be mapped.

The groff language provides several kinds of variables with different interfaces. There are pre-defined variables, but the user can define her own variables as well.

String variables store character sequences. They are set with the request and retrieved by the escape sequences.

Register variables can store numerical values, numbers with a scale unit, and occasionally string-like objects. They are set with the request and retrieved by the escape sequences.

Environments allow the user to temporarily store global formatting parameters like line length, font size, etc. for later reuse. This is done by the request.

Fonts are identified either by a name or by an internal number. The current font is chosen by the request or by the escape sequences. Each device has special fonts, but the following fonts are available for all devices. R is the standard font Roman. B is its bold counterpart. The italic font is called I is everywhere available, but on text devices, it is displayed as an underlined Roman font. For the graphical output devices, there exist constant-width pendants of these font, CR, CI, and CB. On text devices, all characters have a constant width anyway.

Moreover, there are some advanced roff elements. A diversion stores information into a macro for later usage. A trap is a positional condition like a certain number of lines from page top or in a diversion or in the input. Some action can be prescribed to be run automatically when the condition is met.

More detailed information can be found in the groff info file.  

CONTROL CHARACTERS

A dot is only special at the beginning of a line or after the condition in the requests and There it is the control character that introduces a request (or macro). The special behavior can be delayed by using the escape. By using the request, the control character can be set to a different character, making the dot a non-special character.

In all other positions, it just means a dot character. In text paragraphs, it is advantageous to start each sentence at a line of its own.

The single quote has two controlling tasks. At the beginning of a line and in the conditional requests it is the non-breaking control character. That means that it introduces a request like the dot, but with the additional property that this request doesn't cause a linebreak. By using the request, the non-break control character can be set to a different character.

As a second task, it is the most commonly used argument separator in some functional escape sequences (but any pair of characters not part of the argument will work). In all other positions, it denotes the single quote or apostrophe character. Groff provides a printable representation with the escape sequence.

The double quote is used to enclose arguments in requests and macros. In the and requests, a leading double quote in the argument will be stripped off, making everything else afterwards the string to be defined (enabling leading whitespace). The escaped double quote introduces a comment. Otherwise, it is not special. Groff provides a printable representation with the escape sequence.

The backslash usually introduces an escape sequence (this can be changed with the request). A printed version of the escape character is the escape; a backslash glyph can be obtained by

The open parenthesis is only special in escape sequences when introducing an escape name or argument consisting of exactly two characters. In groff, this behavior can be replaced by the [] construct.

The opening bracket is only special in groff escape sequences; there it is used to introduce a long escape name or long escape argument. Otherwise, it is non-special, e.g. in macro calls.

The closing bracket is only special in groff escape sequences; there it terminates a long escape name or long escape argument. Otherwise, it is non-special.

space

Space characters are only functional characters. They separate the arguments in requests or macros, and the words in text lines. They are subject to groff's horizontal spacing calculations. To get a defined space width, escape sequences like (this is the escape character followed by a space), or should be used.

newline

In text paragraphs, newlines mostly behave like space characters. Continuation lines can be specified by an escaped newline, i.e., by specifying a backslash as the last character of a line.

tab

If a tab character occurs during text the interpreter makes a horizontal jump to the next pre-defined tab position. There is a sophisticated interface for handling tab positions.

NUMERICAL EXPRESSIONS

The roff language defines the following scale indicators.

Numerical expressions are combinations of the numerical values defined above with the arithmetical operators ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& (modulo), the comparative operators ��|��� �t& (this is the same as ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& the logical operators ��|��� �t& (and), ��|��� �t& (or), ��|��� �t& (not), and the parentheses ��|��� �t& and ��|��� �t&

Moreover, groff added the following operators for numerical expressions:

For details see the groff info file.  

CONDITIONS

REQUESTS

Most requests take one or more arguments. The arguments are separated by space characters (no tabs!); there is no inherent limit for their length or number. An argument can be enclosed by a pair of double quotes: This is very handy if an argument contains space characters, e.g., ��|��� �t& denotes a single argument.

Some requests have optional arguments with a different behaviour. Not all of these details are outlined here. Refer to the groff info file for all details.

In the following request specifications, most argument names were chosen to be descriptive. Only the following denotations need clarification.

If an expression defined as ��|��� �t& starts with a ��|��� �t& sign the resulting value of the expression will be added to an already existing value inherent to the related request, e.g. adding to a number register. If the expression starts with a ��|��� �t& the value of the expression will be subtracted from the request value.

Without a sign, ��|��� �t& replaces the existing value directly. To assign a negative number either prepend  ��|��� �t& or enclose the negative number in parentheses.  

REQUEST SHORT REFERENCE

Besides these standard groff requests, there might be further macro calls. They can originate from a macro package (see roff(7) for an overview) or from a preprocessor.

Preprocessor macros are easy to be recognized. They enclose their code into a pair of characteristic macros.

ESCAPE SEQUENCES

This is done by enclosing names (escape name and arguments consisting of a variable name) by a pair of brackets ��|��� �t& and constant arguments (number expressions and characters) by apostrophes (ASCII 0x27) like cqconstantcq.

There are abbreviations for short names. Two character escape names can be specified by an opening parenthesis like ��|��� �t& without a closing counterpart. And all one-character names different from the special characters ��|��� �t& and ��|��� �t& can even be specified without a marker in the form ��|��� �t&

Constant arguments of length ��|��� �t& can omit the marker apostrophes, too, but there is no two-character analogue.

While 1-character escape sequences are mainly used for in-line functions and system related tasks, the 2-letter names following the ��|��� �t& construct are used for special characters predefined by the roff system. Names with more than two characters ��|��� �t& mostly denote user defined named characters (see the ��|��� �t& request).  

SINGLE CHARACTER ESCAPES

��|��� �t& Beginning of a comment. Everything up to the end of the line is ignored.

��|��� �t& Everything up to and including the next newline is ignored. This is interpreted in copy mode. This is like ��|��� �t& except the ignoring of the terminating newline.

��|��� �t& The string stored in the string variable with 1-character name ��|��� �t&

��|��� �t& The string stored in the string variable with 2-character name ��|��� �t&

��|��� �t& The string stored in the string variable with arbitrary length name ��|��� �t&

��|��� �t& The name by which the current macro was invoked. The ��|��� �t& request can make a macro have more than one name.

��|��� �t& Macro argument with 1-place number ��|��� �t& where ��|��� �t& is a digit between 1 and 9.

��|��� �t& Macro argument with 2-digit number ��|��� �t&

�ǃ�f�~D Macro argument with number �ǃ�f�~D where �ǃ�f�~D is a numerical expression evaluating to an integer >=1.

�ǃ�f�~D In a macro, the concatenation of all the arguments separated by spaces.

�ǃ�f�~D In a macro, the concatenation of all the arguments with each surrounded by double quotes, and separated by spaces.

�ǃ�f�~D reduces to a single backslash; useful to delay its interpretation as escape character in copy mode. For a printable backslash, use �ǃ�f�~D

�ǃ�f�~D The acute accent ´; same as �ǃ�f�~D Unescaped: apostrophe, right quotation mark, single quote (ASCII 0x27).

�ǃ�f�~D The grave accent `; same as �ǃ�f�~D Unescaped: left quote, backquote (ASCII 0x60).

�ǃ�f�~D The - sign in the current font.

�ǃ�f�~D An uninterpreted dot (period), even at start of line.

�ǃ�f�~D Default optional hyphenation character.

�ǃ�f�~D Transparent line indicator.

�ǃ�f�~D In a diversion, this will transparently embed �ǃ�f�~D in the diversion. �ǃ�f�~D is read in copy mode. See also the escape sequences �ǃ�f�~D and �ǃ�f�~D

�ǃ�f�~D Unpaddable space-size space character (no line break).

�ǃ�f�~D Digit width.

�ǃ�f�~D 1/6 em narrow space character; zero width in nroff.

�ǃ�f�~D 1/12 em half-narrow space character; zero width in nroff.

�ǃ�f�~D Non-printable, zero width character.

�ǃ�f�~D Like �ǃ�f�~D except that it behaves like a character declared with the cflags request to be transparent for the purposes of end of sentence recognition.

�ǃ�f�~D Increases the width of the preceding character so that the spacing between that character and the following character will be correct if the following character is a roman character.

�ǃ�f�~D Modifies the spacing of the following character so that the spacing between that character and the preceding character will correct if the preceding character is a roman character.

�ǃ�f�~D Unbreakable space that stretches like a normal inter-word space when a line is adjusted.

�ǃ�f�~D Inserts a zero-width break point (similar to �ǃ�f�~D but without a soft hyphen character).

�ǃ�f�~D Ignored newline, for continuation lines.

�ǃ�f�~D Begin conditional input.

�ǃ�f�~D End conditional input.

�ǃ�f�~D The special character with 2-character name �ǃ�f�~D see section SPECIAL CHARACTERS.

�ǃ�f�~D The named character with arbitrary length name �ǃ�f�~D

�ǃ�f�~D Non-interpreted leader character.

�ǃ�f�~D If �ǃ�f�~D is acceptable as a name of a string, macro, diversion, register, environment or font it expands to �ǃ�f�~D and �ǃ�f�~D otherwise.

�ǃ�f�~D Bracket building function.

�ǃ�f�~D If �ǃ�f�~D is acceptable as a valid numeric expression it expands to �ǃ�f�~D and �ǃ�f�~D otherwise.

�ǃ�f�~D Interrupt text processing.

�ǃ�f�~D The character called �ǃ�f�~D same as �ǃ�f�~D but compatible to other roff versions.

�ǃ�f�~D Forward (down) 1/2 em vertical unit (1/2 line in nroff).

�ǃ�f�~D Draw a graphical element defined by the characters in �ǃ�f�~D see groff info file for details.

�ǃ�f�~D Printable version of the current escape character.

�ǃ�f�~D Equivalent to an escape character, but is not interpreted in copy-mode.

�ǃ�f�~D Change to font with 1-character name or 1-digit number �ǃ�f�~D

�ǃ�f�~D Change to font with 2-characer name or 2-digit number �ǃ�f�~D

�ǃ�f�~D Change to font with arbitrary length name or number expression �ǃ�f�~D

�ǃ�f�~D Return format of register with name �ǃ�f�~D suitable for �ǃ�f�~D Alternative forms �ǃ�f�~D and �ǃ�f�~D

�ǃ�f�~D Local horizontal motion; move right �ǃ�f�~D (left if negative).

�ǃ�f�~D Set height of current font to �ǃ�f�~D

�ǃ�f�~D Mark horizontal input place in register with arbitrary length name �ǃ�f�~D Alternative forms �ǃ�f�~D and �ǃ�f�~D

�ǃ�f�~D Horizontal line drawing function (optionally using character �ǃ�f�~D

�ǃ�f�~D Vertical line drawing function (optionally using character �ǃ�f�~D

�ǃ�f�~D The numerical value stored in the register variable with the 1-character name �ǃ�f�~D

�ǃ�f�~D The numerical value stored in the register variable with the 2-character name �ǃ�f�~D

�ǃ�f�~D The numerical value stored in the register variable with arbitrary lenght name �ǃ�f�~D

�ǃ�f�~D Typeset the character with code �ǃ�f�~D in the current font, no special fonts are searched. Useful for adding characters to a font using the �ǃ�f�~D request.

�ǃ�f�~D Overstrike characters �ǃ�f�~D �ǃ�f�~D �ǃ�f�~D etc.

�ǃ�f�~D Break and spread output line.

�ǃ�f�~D Reverse 1 em vertical motion (reverse line in nroff).

�ǃ�f�~D The same as �ǃ�f�~D �ǃ�f�~D �ǃ�f�~D

�ǃ�f�~D Set the point size to N scaled points. Note the alternative forms rss±[N], rss'±N', rss±'N', �ǃ�f�~D rss±(xy, �ǃ�f�~D Same as �ǃ�f�~D request.

�ǃ�f�~D Slant output �ǃ�f�~D degrees.

�ǃ�f�~D Non-interpreted horizontal tab.

�ǃ�f�~D Reverse (up) 1/2 em vertical motion (1/2 line in nroff).

�ǃ�f�~D Local vertical motion; move down �ǃ�f�~D (up if negative).

�ǃ�f�~D The contents of the environment variable �ǃ�f�~D Alternative forms �ǃ�f�~D and �ǃ�f�~D

�ǃ�f�~D The width of the character sequence �ǃ�f�~D

�ǃ�f�~D Extra line-space function (negative before, positive after).

�ǃ�f�~D Output �ǃ�f�~D as device control function.

�ǃ�f�~D Output string variable or macro �ǃ�f�~D uninterpreted as device control function. Alternative forms �ǃ�f�~D and �ǃ�f�~D

�ǃ�f�~D Print �ǃ�f�~D with zero width (without spacing).

�ǃ�f�~D Print �ǃ�f�~D and then restore the horizontal and vertical position; �ǃ�f�~D may not contain tabs or leaders.

The escape sequences �ǃ�f�~D �ǃ�f�~D �ǃ�f�~D �ǃ�f�~D �ǃ�f�~D �ǃ�f�~D �ǃ�f�~D �ǃ�f�~D �ǃ�f�~D and �ǃ�f�~D are interpreted in copy mode.

Escape sequences starting with �ǃ�f�~D or �ǃ�f�~D do not represent single character escape sequences, but introduce escape names with two or more characters.

If a backslash is followed by a character that does not constitute a defined escape sequence the backslash is silently ignored and the character maps to itself.  

SPECIAL CHARACTERS

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

�ǃ�f�~D

REGISTERS

Each register is given a name. Arbitrary registers can be defined and set with the request �ǃ�f�~D �ǃ�f�~D

The value stored in a register can be retrieved by the escape sequences introduced by �ǃ�f�~D

Most useful are predefined registers. In the following the notation �ǃ�f�~D is used to refer to a register called �ǃ�f�~D to make clear that we speak about registers. Please keep in mind that the �ǃ�f�~D decoration is not part of the register name.  

READ-ONLY REGISTERS

Post-line extra line-space most recently utilized using �ǃ�f�~D Set to �ǃ�f�~D in troff if option -A is used; always �ǃ�f�~D in nroff. The depth of the last character added to the current environment. It is positive if the character extends below the baseline. The number of lines remaining to be centered, as set by the �ǃ�f�~D request. The height of the last character added to the current environment. It is positive if the character extends above the baseline. The skew of the last character added to the current environment. The skew of a character is how far to the right of the center of a character the center of an accent over that character should be placed. Current vertical place in current diversion; equal to register �ǃ�f�~D Always 1 in GNU troff. Macros should use it to test if running under groff. The current hyphenation language as set by the .hla request. The number of immediately preceding consecutive hyphenated lines. The maximum allowed number of consecutive hyphenated lines, as set by the �ǃ�f�~D request. The current hyphenation flags (as set by the �ǃ�f�~D request). The current hyphenation margin (as set by the �ǃ�f�~D request). The current hyphenation space (as set by the �ǃ�f�~D request). Positive if last output line contains �ǃ�f�~D �ǃ�f�~D if pairwise kerning is enabled, �ǃ�f�~D otherwise. The current ligature mode (as set by the �ǃ�f�~D request). The current line-tabs mode (as set by the �ǃ�f�~D request). The title length (as set by the �ǃ�f�~D request). The amount of space that was needed in the last �ǃ�f�~D request that caused a trap to be sprung. Useful in conjunction with �ǃ�f�~D �ǃ�f�~D if in no-space mode, �ǃ�f�~D otherwise. The number of the next page: either the value set by a �ǃ�f�~D request, or the number of the current page plus 1. The number of lines to be right-justified as set by the rj request. The last requested pointsize in points as a decimal fraction (string-valued). Set to �ǃ�f�~D if option -T is used. A string representation of the current tab settings suitable for use as an argument to the �ǃ�f�~D request. The amount of vertical space truncated by the most recently sprung vertical position trap, or, if the trap was sprung by a �ǃ�f�~D request, minus the amount of vertical motion produced by �ǃ�f�~D request. In other words, at the point a trap is sprung, it represents the difference of what the vertical position would have been but for the trap, and what the vertical position actually is. Useful in conjunction with the �ǃ�f�~D register. The value of the parameters set by the first argument of the �ǃ�f�~D request. The value of the parameters set by the second argument of the �ǃ�f�~D request. �ǃ�f�~D if vertical position traps are enabled, �ǃ�f�~D otherwise. The sum of the number codes of the currently enabled warnings.  

WRITABLE REGISTERS

�ǃ�f�~D Lower left x-coordinate (in PostScript units) of a given PostScript image (set by �ǃ�f�~D Lower left y-coordinate (in PostScript units) of a given PostScript image (set by �ǃ�f�~D �ǃ�f�~D but takes account of the heights and depths of characters. Like �ǃ�f�~D but takes account of the heights and depths of characters. Depth of string below base line (generated by width function �ǃ�f�~D Right skip width from the center of the last character in the �ǃ�f�~D argument. If greater than 0, the maximum number of objects on the input stack. If <=0 there is no limit, i.e., recursion can continue until virtual memory is exhausted. The amount of horizontal space (possibly negative) that should be added to the last character before a subscript (generated by width function �ǃ�f�~D Height of string above base line (generated by width function �ǃ�f�~D The return value of the system() function executed by the last �ǃ�f�~D request. Upper right x-coordinate (in PostScript units) of a given PostScript image (set by �ǃ�f�~D Upper right y-coordinate (in PostScript units) of a given PostScript image (set by �ǃ�f�~D Current year minus 1900. For Y2K compliance use register �ǃ�f�~D instead.  

WARNINGS

The name associated with a warning is used by the �ǃ�f�~D and �ǃ�f�~D options; the number code is used by the �ǃ�f�~D request and by the �ǃ�f�~D register.

�ǃ�f�~D
All warnings except and Intended to cover all warnings with traditional macro packages.

�ǃ�f�~D
In fill mode, lines which could not be broken so that their length was less than the line length. This is enabled by default.

�ǃ�f�~D
Non-existent characters. This is enabled by default.

�ǃ�f�~D
Missing or mismatched closing delimiters.

�ǃ�f�~D
Use of �ǃ�f�~D or �ǃ�f�~D without an argument when there is no current diversion.

�ǃ�f�~D
Use of the �ǃ�f�~D request with no matching �ǃ�f�~D request.

�ǃ�f�~D
Unrecognized escape sequence. Then the escape character is ignored.

�ǃ�f�~D
Non-existent fonts. This is enabled by default.

�ǃ�f�~D
Illegal escapes in text ignored with the �ǃ�f�~D request. These are conditions that are errors when they occur outside of ignored text.

�ǃ�f�~D
Use of undefined strings, macros, and diversions. Automatically handled as empty. Usually, only one warning per name.

�ǃ�f�~D
Request that is missing non-optional arguments.

�ǃ�f�~D
Illegal input character.

�ǃ�f�~D
Invalid numeric expressions. This is enabled by default.

�ǃ�f�~D
Out of range arguments.

�ǃ�f�~D
Use of undefined number register. Automatically defined as having value 0. Usually, only one warning per name.

�ǃ�f�~D
Use of �ǃ�f�~D where a number was expected.

�ǃ�f�~D
Meaningless scaling indicators.

�ǃ�f�~D
Missing space between a request or macro and its argument. Then no macro is automatically defined. This is enabled by default. This warning will never occur in compatibility mode.

�ǃ�f�~D
Dubious syntax in numeric expressions.

�ǃ�f�~D
Inappropriate use of a tab character (either in an unquoted macro argument or where a number was expected).

�ǃ�f�~D
All warnings.

Bit Code Warning Bit Code Warning Bit Code Warning 0 1 char 8 256 di 16 65536 space 1 2 number 9 512 mac 17 131072 font 2 4 break 10 1024 reg 18 262144 ig 3 8 delim 11 2048 tab 4 16 el 12 4096 right-brace 5 32 scale 13 8192 missing 6 64 range 14 16384 input 7 128 syntax 15 32768 escape

COMPATIBILITY

Compatibility mode can be turned on with the ��|��� �t& command line option, and turned on or off with the ��|��� �t& request. The number register ��|��� �t& is ��|��� �t& if compatibility mode is on, ��|��� �t& otherwise.

This became necessary because the GNU concept for long names causes some incompatibilities. Classical troff will interpret

.dsabcd

as defining a string ab with contents cd. Normally, groff will interpret this as a call of a macro named ��|��� �t&

Also classical troff will interpret ��|��� �t& or ��|��� �t& as references to a string or number register called ��|��� �t& In GNU native mode, however, this will normally be interpreted as the start of a long name.

In compatibility mode, groff will interpret these things in the traditional way, but long names are not recognized.

On the other hand, groff in GNU native mode does not allow to use the escape sequences ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& and ��|��� �t& in names of strings, macros, diversions, number registers, fonts or environments, whereas classical troff does. The ��|��� �t& escape sequence can be helpful in avoiding these escape sequences in names.

Fractional pointsizes cause one noteworthy incompatibility. In classical troff, the ��|��� �t& request ignores scale indicators and so

.ps 10u

will set the pointsize to 10 points, whereas in groff native mode the pointsize will be set to 10 scaled points.

In groff mode, there is a fundamental difference between unformatted input characters, and formatted output characters. Everything that affects how an output character will be output is stored with the character; once an output character has been constructed it is unaffected by any subsequent requests that are executed, including the ��|��� �t& ��|��� �t& ��|��� �t& ��|��� �t& or ��|��� �t& requests.

Normally output characters are constructed from input characters at the moment immediately before the character is added to the current output line. Macros, diversions and strings are all, in fact, the same type of object; they contain lists of input characters and output characters in any combination.

An output character does not behave like an input character for the purposes of macro processing; it does not inherit any of the special properties that the input character from which it was constructed might have had. The following example will make things clearer.

.di x
rsrsrsrs
.br
.di
.x

In GNU mode this will be printed as ��|��� �t& So each pair of input backslashes ��|��� �t& is turned into a single output backslash ��|��� �t& and the resulting output backslashes are not interpreted as escape characters when they are reread.

Classical troff would interpret them as escape characters when they were reread and would end up printing a single backslash ��|��� �t&

The correct way to get a printable ��|��� �t& is to use the ��|��� �t& escape sequence. This will always print a single instance of the current escape character, regardless of whether or not it is used in a diversion. It will also work in both GNU mode and compatibility mode.

To store an escape sequence in a diversion that will be interpreted when the diversion is reread, either the traditional ��|��� �t& transparent output facility or the new ��|��� �t& escape sequence can be used.  

BUGS

The WARNINGS section belongs to troff(1).  

AUTHOR

It is distributed under the terms of the FDL (GNU Free Documentation License) version 1.1 or later. You should have received a copy of the FDL on your system, it is also available on-line under

http://www.gnu.org/copyleft/fdl.html.

Formerly, the extensions of the groff language were kept in the manual page troff(1). This document contains the essential parts of that documentation, but the gory details are found in the groff info file.  

SEE ALSO

For a survey of roff and the groff system and further documentation pointers see roff(7).

The formatter programs are described in groff(1) and troff(1); a complete of all predefined glyph names can be found in groff_char(7).

The classical troff documentation is available on-line at

http://cm.bell-labs.com/cm/cs/cstr.html

http://www.kohala.com/start/troff/.

Index

NAME

DESCRIPTION

GROFF ELEMENTS

CONTROL CHARACTERS

NUMERICAL EXPRESSIONS

CONDITIONS

REQUESTS

REQUEST SHORT REFERENCE

ESCAPE SEQUENCES

SINGLE CHARACTER ESCAPES

SPECIAL CHARACTERS

REGISTERS

READ-ONLY REGISTERS

WRITABLE REGISTERS

WARNINGS

COMPATIBILITY

BUGS

AUTHOR

SEE ALSO