1 '\" e -- preprocess: eqn(1)
5 Copyright (c) 2014 - 2017 Steffen (Daode) Nurpmeso <steffen@sdaoden.eu>.
7 Copyright (C) 1989, 2001 - 2008
8 Free Software Foundation, Inc.
9 rewritten from scrach 2001 by Bernd Warken <bwarken@mayn.de>
11 Permission is granted to copy, distribute and/or modify this document
12 under the terms of the GNU Free Documentation License, Version 1.1 or
13 any later version published by the Free Software Foundation; with the
14 Invariant Sections being this .ig-section and AUTHORS, with no
15 Front-Cover Texts, and with no Back-Cover Texts.
17 You should have received a copy of the Free Documentation License
18 as part of the file COPYING; also located in the main directory of the
19 source package of this program.
22 .\" ----------------- Document configuration
24 .\" Number register to decide whether the commands `{' and `}' are used
25 .\" 0: disable (actual default); 1: enable
29 Unfortunately, old versions of groff used an illogical position change
30 after some D\~commands (Dp, DP, Dt). If the number register
31 @STUPID_DRAWING_POSITIONING is 1 (actual default) then change position
32 after these commands, otherwise the position is not changed.
34 .nr @STUPID_DRAWING_POSITIONING 1
36 .\" ----------------- Semantical definitions
39 .ds @backslash \[rs]\"
40 .ds @linebreak \fR\[la]line-break\[ra]\fP\"
42 .\" Begin of macro definitions
45 .RI ( \,\\$1\/ ,\ \,\\$2\/ )\\$3
48 .offset \fI\\$1\/\fP\d\s-3\\$2\s+3\u\x'\n[.v]/4' \fI\\$3\/\fP\d\s-3\\$4\s+3\u\x'\n[.v]/4' \\$5\x'\n[.v]/4'
50 .\" format: .command <name> "<arguments>" <punctuation>
52 \fB\\$1\fP\ \fI\,\\$2\/\fP\\$3
54 .\" format: .D-command <subcommand> "<arguments>"
56 \fBD\\$1\fP\ \fI\,\\$2\/\fP\|\*[@linebreak]
59 .\" We set these as troff micromotions rather than eqn because \d and \u
60 .\" can be lifted to XML subscript/superscript tags. Don't change
61 .\" these to a parameterized string, man2html won't handle that.
62 .ds hv1 \fIh\d\s-3\&1\s+3\u\~v\d\s-3\&1\s+3\u\fP\x'\n[.v]/4'
63 .ds hv2 \fIh\d\s-3\&2\s+3\u\~v\d\s-3\&2\s+3\u\fP\x'\n[.v]/4'
64 .ds hvn \fIh\d\s-3\&n\s+3\u\~v\d\s-3\&n\s+3\u\fP\x'\n[.v]/4'
67 \fBDa\fP\ \*[hv1] \*[hv2]\|\*[@linebreak]
69 .\" graphics command .D with a variable number of arguments
70 .\" format: .D-multiarg <subcommand>
72 \fBD\\$1\fP\ \*[hv1] \*[hv2] .\|.\|. \*[hvn]\|\*[@linebreak]
74 .\" format: .x-command <subname> "<arguments>"
76 \fBx\\$1\fP\ \fI\\$2\fP\|\*[@linebreak]
79 .RI "(" "\\$1" " control command)"
82 .\" End of macro definitions
85 .TH @U_ROFF@-OUT @MAN5EXT@ "@MDATE@" "@T_ROFF@ v@VERSION@"
88 @L_ROFF@-out \- @T_ROFF@ intermediate output format
93 This manual page describes the
94 .I intermediate output
96 .BR @L_ROFF@ (@MAN7EXT@)
97 text processing system
98 .BR @L_ROFF@ (@MAN1EXT@),
99 as produced by a run of the
100 .BR @L_TROFF@ (@MAN1EXT@)
103 It contains already all device-specific information, but it is not yet
104 fed into a device postprocessor program.
105 Because of this it is called intermediate.
109 program provides the option
111 to inhibit postprocessing, such that the produced
112 .I intermediate output
113 is sent to standard output just like calling
119 In this document, the term
121 describes what is output by the
124 .I intermediate output
125 refers to the language that is accepted by the parser that prepares
126 this output for the postprocessors.
128 This parser is smarter on whitespace and implements obsolete elements
129 for compatibility, otherwise both formats are the same.
133 The main purpose of the
134 .I intermediate output
135 concept is to facilitate the development of postprocessors by
136 providing a common programming interface for all devices.
138 It has a language of its own that is completely different from the
139 .BR @L_ROFF@ (@MAN7EXT@)
144 language is a high-level programming language for text processing, the
145 .I intermediate output
146 language is a kind of low-level assembler language by specifying all
147 positions on the page for writing and drawing.
154 versions are denoted as
158 .I intermediate output
161 output was hard to understand because of strange habits.
164 .SH "LANGUAGE CONCEPTS"
170 input is cracked down to the information on what has to be printed at
171 what position on the intended device.
173 So the language of the
174 .I intermediate output
175 format can be quite small.
177 Its only elements are commands with or without arguments.
179 In this document, the term \[lq]command\[rq] always refers to the
180 .I intermediate output
181 language, never to the
183 language used for document formatting.
185 There are commands for positioning and text writing, for drawing, and
186 for device controlling.
191 .I Classical troff output
192 had strange requirements on whitespace.
196 output parser, however, is smart about whitespace by making it
199 The whitespace characters, i.e., the
204 characters, always have a syntactical meaning.
206 They are never printable because spacing within the output is always
207 done by positioning commands.
215 characters is treated as a single
219 It separates commands and arguments, but is only required when there
220 would occur a clashing between the command code and the arguments
223 Most often, this happens when variable length command names,
224 arguments, argument lists, or command clusters meet.
226 Commands and arguments with a known, fixed length need not be
233 A line break is a syntactical element, too.
235 Every command argument can be followed by whitespace, a comment, or a
239 .I syntactical line break
240 is defined to consist of optional
242 that is optionally followed by a comment, and a newline character.
246 The normal commands, those for positioning and text, consist of a
247 single letter taking a fixed number of arguments.
249 For historical reasons, the parser allows to stack such commands on
250 the same line, but fortunately, in
251 .I @T_ROFF@ intermediate
253 every command with at least one argument is followed by a line break,
254 thus providing excellent readability.
257 The other commands \[em] those for drawing and device controlling \[em]
258 have a more complicated structure; some recognize long command names,
259 and some take a variable number of arguments.
265 commands were designed to request a
266 .I syntactical line break
267 after their last argument.
271 has an argument that can stretch over several lines, all other
272 commands must have all of their arguments on the same line as the
273 command, i.e., the arguments may not be split by a line break.
276 Empty lines, i.e., lines containing only space and/or a comment, can
279 They are just ignored.
286 Some commands take integer arguments that are assumed to represent
287 values in a measurement unit, but the letter for the corresponding
289 is not written with the output command arguments; see
290 .BR @L_ROFF@ (@MAN7EXT@)
291 for more on this topic.
293 Most commands assume the scale indicator\~\c
295 the basic unit of the device, some use\~\c
299 of the device, while others, such as the color commands expect plain
302 Note that these scale indicators are relative to the chosen device.
304 They are defined by the parameters specified in the device's
307 .BR @L_ROFF@-font (@MAN5EXT@).
311 Note that single characters can have the eighth bit set, as can the
312 names of fonts and special characters (this is, glyphs).
314 The names of glyphs and fonts can be of arbitrary length.
316 A glyph that is to be printed will always be in the current font.
320 A string argument is always terminated by the next whitespace
321 character (space, tab, or newline); an embedded
323 character is regarded as part of the argument, not as the beginning of
326 An integer argument is already terminated by the next non-digit
327 character, which then is regarded as the first character of the next
335 .I intermediate output
336 document consists of two parts, the
344 is to set the general device parameters using three exactly specified
349 is guaranteed to consist of the following three lines (in that order):
361 with the arguments set as outlined in the section
362 .BR "Device Control Commands" .
364 However, the parser for the
365 .I intermediate output
366 format is able to swallow additional whitespace and comments as well.
372 is the main section for processing the document data.
374 Syntactically, it is a sequence of any commands different from the
378 Processing is terminated as soon as the first
380 command is encountered; the last line of any
381 .I @T_ROFF@ intermediate output
382 always contains such a command.
390 A new page is started by a
393 Positioning, writing, and drawing commands are always done within the
394 current page, so they cannot occur before the first
397 Absolute positioning (by the
401 is done relative to the current page, all other positioning
402 is done relative to the current location within this page.
405 .SH "COMMAND REFERENCE"
407 This section describes all
408 .I intermediate output
409 commands, the classical commands as well as the
414 .SS "Comment Command"
417 .BI # anything \[la]end-of-line\[ra]
420 Ignore any characters from the
422 character up to the next newline character.
425 This command is the only possibility for commenting in the
429 Each comment can be preceded by arbitrary
432 every command can be terminated by a comment.
436 .SS "Simple Commands"
439 The commands in this subsection have a command code consisting of a
440 single character, taking a fixed number of arguments.
442 Most of them are commands for positioning and text writing.
444 These commands are smart about whitespace.
448 can be inserted before, after, and between the command letter and its
451 All of these commands are stackable, i.e., they can be preceded by
452 other simple commands or followed by arbitrary other commands on the
457 is only necessary when two integer arguments would clash or if the
458 preceding argument ends with a string argument.
461 .if \n[@USE_ENV_STACK]=1 \{\
464 Open a new environment by copying the actual device configuration data
465 to the environment stack.
467 The current environment is setup by the device specification and
468 manipulated by the setting commands.
473 Close the actual environment (opened by a preceding
475 and restore the previous environment from the environment
476 stack as the actual device configuration data.
478 .\} \" endif @USE_ENV_STACK
482 .command C xxx \[la]white-space\[ra]
483 Print a glyph (special character) named
490 is necessary to allow glyph names of arbitrary length.
492 The glyph is printed at the current print position; the
493 glyph's size is read from the font file.
495 The print position is not changed.
500 Print glyph with single-letter name\~\c
502 at the current print position;
503 the glyph's size is read from the font file.
505 The print position is not changed.
510 Set font to font number\~\c
512 (a non-negative integer).
517 Move right to the absolute vertical position\~\c
519 (a non-negative integer in basic units\~\c
521 relative to left edge of current page.
528 (a non-negative integer) basic units\~\c
530 horizontally to the right.
533 allows negative values for
541 .command m "color-scheme \fR[\fPcomponent .\|.\|.\fR]\fP"
542 Set the color for text (glyphs), line drawing, and the outline of
543 graphic objects using different color schemes; the analoguous command
544 for the filling color of graphic objects is
547 The color components are specified as integer arguments between 0 and
550 The number of color components and their meaning vary for the
551 different color schemes.
553 These commands are generated by the escape sequence
554 .BR \*[@backslash]m .
556 No position changing.
566 .command mc "cyan magenta yellow"
567 Set color using the CMY color scheme, having the 3\~color components
568 cyan, magenta, and yellow.
573 Set color to the default color value
574 (black in most cases).
576 No component arguments.
581 Set color to the shade of gray given by the argument, an integer
582 between 0 (black) and \n[@maxcolor] (white).
586 .command mk "cyan magenta yellow black"
587 Set color using the CMYK color scheme, having the 4\~color components
588 cyan, magenta, yellow, and black.
591 .command mr "red green blue"
592 Set color using the RGB color scheme, having the 3\~color components
593 red, green, and blue.
600 Print glyph with index\~\c
602 (an integer, normally non-negative) of the current font.
604 The print position is not changed.
610 is used, negative values are emitted also to indicate an unbreakable space
615 represents an unbreakable space which has a width of 193\|u.
624 Inform the device about a line break, but no positioning is done by
630 the integer arguments
634 informed about the space before and after the current line to
636 .I intermediate output
637 more human readable without performing any action.
641 they are just ignored, but they must be provided for compatibility
647 Begin a new page in the outprint.
649 The page number is set to\~\c
652 This page is completely independent of pages formerly processed even
653 if those have the same page number.
655 The vertical position on the outprint is automatically set to\~0.
657 All positioning, writing, and drawing is always done relative to a
660 must be issued before any of these commands.
683 .command t xyz\|.\|.\|. \[la]white-space\[ra]
685 .command t "xyz\|.\|.\|.\& dummy-arg" \[la]white-space\[ra]
686 Print a word, i.e., a sequence of glyphs with single-letter names
690 etc., terminated by a space character or a line break; an optional
691 second integer argument is ignored (this allows the formatter to
692 generate an even number of arguments).
694 The first glyph should be printed at the current position, the
695 current horizontal position should then be increased by the width of
696 the first glyph, and so on for each glyph.
698 The widths of the glyph are read from the font file, scaled for the
699 current point size, and rounded to a multiple of the horizontal
702 Special characters (glyphs with names longer than a single letter)
703 cannot be printed using this command; use the
705 command for those glyphs.
709 extension; it is only used for devices whose
714 .BR @L_ROFF@-font (@MAN5EXT@).
718 .command u "n xyz\|.\|.\|." \[la]white-space\[ra]
719 Print word with track kerning.
721 This is the same as the
723 command except that after printing each glyph, the current
724 horizontal position is increased by the sum of the width of that
732 extension; it is only used for devices whose
737 .BR @L_ROFF@-font (@MAN5EXT@).
742 Move down to the absolute vertical position\~\c
744 (a non-negative integer in basic units\~\c
746 relative to upper edge of current page.
757 is a non-negative integer).
760 allows negative values for
769 Informs about a paddable whitespace to increase readability.
771 The spacing itself must be performed explicitly by a move command.
775 .SS "Graphics Commands"
778 Each graphics or drawing command in the
779 .I intermediate output
780 starts with the letter\~\c
782 followed by one or two characters that specify a subcommand; this
783 is followed by a fixed or variable number of integer arguments that
784 are separated by a single space character.
789 may not be followed by another command on the same line (apart from a
800 output follows the classical spacing rules (no space between command
801 and subcommand, all arguments are preceded by a single space
802 character), but the parser allows optional space between the command
803 letters and makes the space before the first argument optional.
805 As usual, each space can be any sequence of tab and space characters.
809 Some graphics commands can take a variable number of arguments.
811 In this case, they are integers representing a size measured in basic
818 stand for horizontal distances where positive means right, negative
824 stand for vertical distances where positive means down, negative up.
826 All these distances are offsets relative to the current location.
830 Unless indicated otherwise, each graphics command directly corresponds
834 .BR @L_ROFF@ (@MAN7EXT@).
840 \~commands are assumed to be device-specific.
842 Its arguments are parsed as strings; the whole information is then
843 sent to the postprocessor.
847 In the following command reference, the syntax element
848 .I \[la]line-break\[ra]
850 .I syntactical line break
851 as defined in section
857 Draw B-spline from current position to offset
858 .indexed_offset h 1 v 1 ,
860 .indexed_offset h 2 v 2
861 if given, etc., up to
862 .indexed_offset h n v n .
863 This command takes a variable number of argument pairs; the current
864 position is moved to the terminal point of the drawn curve.
869 Draw arc from current position to
870 .indexed_offset h 1 v 1 \|+\|\c
871 .indexed_offset h 2 v 2
873 .indexed_offset h 1 v 1 ;
874 then move the current position to the final point of the arc.
880 .D-command C "d dummy-arg"
881 Draw a solid circle using the current fill color with diameter\~\c
883 (integer in basic units\~\c
885 with leftmost point at the current position; then move the current
886 position to the rightmost point of the circle.
888 An optional second integer argument is ignored (this allows to the
889 formatter to generate an even number of arguments).
898 Draw circle line with diameter\~\c
900 (integer in basic units\~\c
902 with leftmost point at the current position; then move the current
903 position to the rightmost point of the circle.
908 Draw a solid ellipse in the current fill color with a horizontal
911 and a vertical diameter of\~\c
913 (both integers in basic units\~\c
915 with the leftmost point at the current position; then move to the
916 rightmost point of the ellipse.
925 Draw an outlined ellipse with a horizontal diameter of\~\c
927 and a vertical diameter of\~\c
929 (both integers in basic units\~\c
931 with the leftmost point at current position; then move to the
932 rightmost point of the ellipse.
936 .D-command F "color-scheme \fR[\fPcomponent .\|.\|.\fR]\fP"
937 Set fill color for solid drawing objects using different color
938 schemes; the analoguous command for setting the color of text, line
939 graphics, and the outline of graphic objects is
942 The color components are specified as integer arguments between 0 and
945 The number of color components and their meaning vary for the
946 different color schemes.
948 These commands are generated by the
950 .BR \*[@backslash]D'F\ .\|.\|. '
953 (with no other corresponding graphics commands).
955 No position changing.
965 .D-command Fc "cyan magenta yellow"
966 Set fill color for solid drawing objects using the CMY color scheme,
967 having the 3\~color components cyan, magenta, and yellow.
972 Set fill color for solid drawing objects to the default fill color value
973 (black in most cases).
975 No component arguments.
980 Set fill color for solid drawing objects to the shade of gray given by
981 the argument, an integer between 0 (black) and \n[@maxcolor] (white).
985 .D-command Fk "cyan magenta yellow black"
986 Set fill color for solid drawing objects using the CMYK color scheme,
987 having the 4\~color components cyan, magenta, yellow, and black.
990 .D-command Fr "red green blue"
991 Set fill color for solid drawing objects using the RGB color scheme,
992 having the 3\~color components red, green, and blue.
1001 must be an integer in the range \-32767 to 32767.
1005 .RI 0\|\[<=]\| n \|\[<=]\|1000
1006 Set the color for filling solid drawing objects to a shade of gray,
1007 where 0 corresponds to solid white, 1000 (the default) to solid black,
1008 and values inbetween to intermediate shades of gray; this is
1009 obsoleted by command
1013 .IR n "\|<\|0 or " n \|>\|1000
1014 Set the filling color to the color that is currently being used for
1015 the text and the outline, see command
1017 For example, the command sequence
1022 mg 0 0 \n[@maxcolor]
1028 sets all colors to blue.
1031 No position changing.
1042 Draw line from current position to offset
1044 (integers in basic units\~\c
1046 then set current position to the end of the drawn line.
1051 Draw a polygon line from current position to offset
1052 .indexed_offset h 1 v 1 ,
1053 from there to offset
1054 .indexed_offset h 2 v 2 ,
1056 .indexed_offset h n v n ,
1057 and from there back to the starting position.
1059 .ie \n[@STUPID_DRAWING_POSITIONING]=1 \{\
1060 For historical reasons, the position is changed by adding the sum of
1061 all arguments with odd index to the actual horizontal position and the
1062 even ones to the vertical position.
1064 Although this doesn't make sense it is kept for compatibility.
1068 As the polygon is closed, the end of drawing is the starting point, so
1069 the position doesn't change.
1079 The same macro as the corresponding
1081 command with the same arguments, but draws a solid polygon in the
1082 current fill color rather than an outlined polygon.
1084 .ie \n[@STUPID_DRAWING_POSITIONING]=1 \{\
1085 The position is changed in the same way as with
1089 No position changing.
1098 Set the current line thickness to\~\c
1100 (an integer in basic units\~\c
1106 select the smallest available line thickness; if
1108 set the line thickness proportional to the point size (this is the
1109 default before the first
1111 command was specified).
1113 .ie \n[@STUPID_DRAWING_POSITIONING]=1 \{\
1114 For historical reasons, the horizontal position is changed by adding
1115 the argument to the actual horizontal position, while the vertical
1116 position is not changed.
1118 Although this doesn't make sense it is kept for compatibility.
1122 No position changing.
1130 .SS "Device Control Commands"
1133 Each device control command starts with the letter
1135 followed by a space character (optional or arbitrary space/\:tab in
1137 and a subcommand letter or word; each argument (if any) must be
1144 commands are terminated by a
1145 .IR "syntactical line break" ;
1146 no device control command can be followed by another command on the same
1147 line (except a comment).
1150 The subcommand is basically a single letter, but to increase
1151 readability, it can be written as a word, i.e., an arbitrary sequence
1152 of characters terminated by the next tab, space, or newline character.
1154 All characters of the subcommand word but the first are simply ignored.
1158 outputs the initialization command
1162 and the resolution command
1169 are accepted as well to mean the same commands.
1172 In the following, the syntax element
1173 .I \[la]line-break\[ra]
1175 .I syntactical line break
1176 as defined in section
1184 as the intended name for the current file in error reports.
1186 This is useful for remembering the original file name when
1187 an internal piping mechanism is used.
1188 The input file is not changed by this command.
1198 Mount font position\~\c
1200 (a non-negative integer) with font named\~\c
1204 .BR @L_ROFF@-font (@MAN5EXT@).
1210 Set character height to\~\c
1212 (a positive integer in scaled points\~\c
1216 used the unit points (\c
1218 instead; see section
1227 This is the third command of the
1236 The classical documentation reads
1237 .I pause device, can be
1242 .x-command r "n\ h\ v"
1248 is the minimal horizontal motion, and
1250 the minimal vertical motion possible with this device; all arguments
1251 are positive integers in basic units\~\c
1255 This is the second command of the
1264 degrees (an integer in basic units\~\c
1271 Terminates the processing of the current file; issued as the last
1273 .I intermediate @L_TROFF@
1280 Generate trailer information, if any.
1284 this is actually just ignored.
1290 Set name of device to word
1292 a sequence of characters ended by the next whitespace character.
1294 The possible device names coincide with those from the @L_ROFF@
1298 This is the first command of the
1305 Configure underlining of spaces.
1309 is\~1, start underlining of spaces;
1312 is\~0, stop underlining of spaces.
1314 This is needed for the
1318 mode and is ignored otherwise.
1326 .x-command X anything
1330 uninterpreted to the device.
1332 If the line following this command starts with a
1334 character this line is interpreted as a continuation line in the
1339 is ignored, but a newline character is sent instead to the device, the
1340 rest of the line is sent uninterpreted.
1342 The same applies to all following lines until the first character of a
1347 This command is generated by the escape sequence
1348 .BR \*[@backslash]X .
1350 The line-continuing feature is a
1356 .SS "Obsolete Command"
1361 output, emitting a single glyph was mostly done by a very
1362 strange command that combined a horizontal move and the printing of a
1365 It didn't have a command code, but is represented by a 3-character
1366 argument consisting of exactly 2\~digits and a character.
1372 (exactly two decimal digits) basic units\~\c
1374 then print glyph with single-letter name\~\c
1383 .I syntactical space
1384 around and within this command is allowed to be added.
1386 Only when a preceding command on the same line ends with an argument
1387 of variable length a separating space is obligatory.
1392 large clusters of these and other commands were used, mostly without
1393 spaces; this made such output almost unreadable.
1399 For modern high-resolution devices, this command does not make sense
1400 because the width of the glyphs can become much larger than two
1406 provide a better functionality.
1409 .SH "POSTPROCESSING"
1413 postprocessors are programs that have the task to translate the
1414 .I intermediate output
1415 into actions that are sent to a device.
1417 A device can be some piece of hardware such as a printer, or a software
1418 file format suitable for graphical or text processing.
1422 system provides powerful means that make the programming of such
1423 postprocessors an easy task.
1425 There is a library function that parses the
1426 .I intermediate output
1427 and sends the information obtained to the device via methods of a
1428 class with a common interface for each device.
1430 So a postprocessor must only redefine the methods of this class.
1432 For details, see the reference in section
1438 This section presents the
1439 .I intermediate output
1440 generated from the same input for three different devices.
1442 The input is the sentence
1446 on the command line.
1450 High-resolution device
1457 \fBshell>\fP echo "hell world" | @L_ROFF@ \-Z \-T ps
1488 This output can be fed into the postprocessor
1489 .BR @L_D_PS@ (@MAN1EXT@)
1490 to get its representation as a PostScript file.
1494 Low-resolution device
1500 This is similar to the high-resolution device except that the
1501 positioning is done at a minor scale.
1503 Some comments (lines starting with
1505 were added for clarification; they were not generated by the
1511 \fBshell>\fP "hell world" | @L_ROFF@ \-Z \-T latin1
1522 .I "# begin a new page"
1530 .I "# initial positioning on the page"
1534 .I "# write text `hell'"
1537 .I "# inform about a space, and do it by a horizontal jump"
1540 .I "# write text `world'"
1543 .I "# announce line break, but do nothing because ..."
1546 .I "# ... the end of the document has been reached"
1557 This output can be fed into the postprocessor
1558 .BR @L_D_TTY@ (@MAN1EXT@)
1559 to get a formatted text document.
1564 Due to the obsolete jump-and-write command, the text clusters in the
1565 classical output are almost unreadable.
1571 .I intermediate output
1574 was first documented in
1578 .I @T_ROFF@ intermediate output
1579 format is compatible with this specification except for the following
1584 The classical quasi device independence is not yet implemented.
1588 The old hardware was very different from what we use today.
1592 devices are also fundamentally different from the ones in
1596 For example, the classical PostScript device was called
1598 and had a resolution of 720 units per inch,
1602 device has a resolution of 72000 units per inch.
1604 Maybe, by implementing some rescaling mechanism similar to the
1605 classical quasi device independence, these could be integrated into
1611 The B-spline command
1613 is correctly handled by the
1614 .I intermediate output
1615 parser, but the drawing routines aren't implemented in some of the
1616 postprocessor programs.
1620 The argument of the commands
1624 has the implicit unit scaled point\~\c
1633 This isn't an incompatibility, but a compatible extension, for both
1634 units coincide for all devices without a
1636 parameter, including all classical and the
1642 devices with a sizescale parameter either did not exist, had a
1643 different name, or seem to have had a different resolution.
1645 So conflicts with classical devices are very unlikely.
1648 .ie \n[@STUPID_DRAWING_POSITIONING]=1 \{\
1650 The position changing after the commands
1655 is illogical, but as old versions of GNU troff used this feature it is
1656 kept for compatibility reasons.
1657 .\} \" @STUPID_DRAWING_POSITIONING
1660 Temporarily, there existed some confusion on the positioning after the
1666 This has been clarified by establishing the classical rule for all
1667 @T_ROFF@ drawing commands:
1673 The position after a graphic object has been drawn is at its end;
1674 for circles and ellipses, the "end" is at the right side.
1680 From this, the positionings specified for the drawing commands above
1681 follow quite naturally.
1682 .\} \" @STUPID_DRAWING_POSITIONING
1685 The differences between
1690 .BR @L_ROFF@-diff (@MAN7EXT@).
1696 .BI @FONTDIR@/dev name /DESC
1697 Device description file for device
1701 .IB \[la]@T_ROFF@-source-dir\[ra] /src/libs/driver/input.cpp
1702 Defines the parser and postprocessor for the
1706 It is located relative to the top directory of the
1710 This parser is the definitive specification of the
1711 .I @T_ROFF@ intermediate output
1718 .BR @L_ROFF@ (@MAN7EXT@)
1719 refers to a manual page; here
1723 of the man-page documentation system.
1725 To read the example, look up section\~@MAN7EXT@ in your desktop help
1726 system or call from the shell prompt
1731 \fBshell>\fP man @MAN7EXT@ @L_ROFF@
1737 For more details, see
1742 .BR @L_ROFF@ (@MAN1EXT@)
1745 and further readings.
1749 .BR @L_ROFF@ (@MAN7EXT@)
1750 for details of the language such as numerical units and escape sequences.
1754 .BR @L_ROFF@-font (@MAN5EXT@)
1755 for details on the device scaling parameters of the
1761 .BR @L_TROFF@ (@MAN1EXT@)
1762 generates the device-independent intermediate output.
1766 .BR @L_ROFF@-history (@MAN7EXT@)
1767 for historical aspects and the general structure of roff systems.
1771 .BR @L_ROFF@-diff (@MAN7EXT@)
1772 The differences between the intermediate output in groff and classical
1776 .BR \%@L_D_DVI@ (@MAN1EXT@),
1777 .BR \%@L_D_HTML@ (@MAN1EXT@),
1778 .BR \%@L_D_PS@ (@MAN1EXT@),
1779 .BR \%@L_D_TTY@ (@MAN1EXT@)
1782 the @T_ROFF@ postprocessor programs.
1788 .I classical troff output language
1789 is described in two AT&T Bell Labs CSTR documents available on-line at
1790 .UR http://\:cm.bell-labs.com/\:cm/\:cs/\:cstr.html
1797 .I A Typesetter-independent TROFF
1800 is the original and most comprehensive documentation on the output
1802 .UR http://\:cm.bell-labs.com/\:cm/\:cs/\:cstr/\:97.ps.gz
1809 The 1992 revision of the
1810 .I Nroff/\:Troff User's Manual
1812 .I J.\& F.\& Ossanna
1815 isn't as comprehensive as
1817 regarding the output language; see
1818 .UR http://\:cm.bell-labs.com/\:cm/\:cs/\:cstr/\:54.ps.gz
1825 Copyright (c) 2014 - 2017 Steffen (Daode) Nurpmeso <steffen@sdaoden.eu>.
1827 Copyright (C) 1989, 2001 - 2008
1828 Free Software Foundation, Inc.
1831 This document is distributed under the terms of the FDL (GNU Free
1832 Documentation License) version 1.1 or later.
1834 You should have received a copy of the FDL with this package; it is also
1835 available on-line at the
1836 .UR http://\:www.gnu.org/\:copyleft/\:fdl.html
1842 This document was rewritten in 2002 by Bernd Warken.