3 \C{output} Halibut output formats
5 This chapter describes each of Halibut's current \i{output formats}.
6 It gives some general information about the format, and also
7 describes all the \i{configuration directives} which are specific to
10 \H{output-text} Plain text
12 This output format generates the document as a single \i{plain text}
13 file. No table of contents or index is generated.
15 The precise formatting of the text file can be controlled by a
16 variety of configuration directives. They are listed in the
17 following subsections.
19 \S{output-text-file} Output file name
21 \dt \I{\cw{\\cfg\{text-filename\}}}\cw{\\cfg\{text-filename\}\{}\e{filename}\cw{\}}
23 \dd Sets the \i{output file name} in which to store the text file.
24 This directive is implicitly generated if you provide a file name
25 parameter after the command-line option \i\c{--text} (see
28 \S{output-text-dimensions} Indentation and line width
30 This section describes the configuration directives which control
31 the \i{horizontal dimensions} of the output text file: how much
32 paragraphs are indented by and how long the lines are.
34 \dt \I{\cw{\\cfg\{text-width\}}}\cw{\\cfg\{text-width\}\{}\e{width}\cw{\}}
36 \dd Sets the \I{text width}width of the main part of the document,
37 in characters. This width will be used for wrapping paragraphs and
38 for centring titles (if you have asked for titles to be centred -
39 see \k{output-text-headings}). This width does \e{not} include the
40 left indentation set by \cw{\\cfg\{text-indent\}}; if you specify an
41 indent of 8 and a width of 64, your maximum output line length will
44 \dt \I{\cw{\\cfg\{text-indent\}}}\cw{\\cfg\{text-indent\}\{}\e{indent}\cw{\}}
46 \dd Sets the left \i{indentation} for the document. If you set this
47 to zero, your document will look like an ordinary text file as
48 someone with a text editor might have written it; if you set it
49 above zero, the text file will have a \i{margin} down the left in
50 the style of some printed manuals, and you can then configure the
51 section numbers to appear in this margin (see
52 \k{output-text-headings}).
54 \dt \I{\cw{\\cfg\{text-indent-code\}}}\cw{\\cfg\{text-indent-code\}\{}\e{indent}\cw{\}}
56 \dd Specifies how many extra characters of indentation (on top of
57 the normal left indent) should be given to \I{code paragraphs,
58 indentation} code paragraphs.
60 \dt \I{\cw{\\cfg\{text-list-indent\}}}\cw{\\cfg\{text-list-indent\}\{}\e{indent}\cw{\}}
62 \dd Specifies how many extra spaces should be used to indent the
63 bullet or number in a \I{bulletted list, indentation}bulletted or
64 \I{numbered list, indentation}numbered \I{list, indentation}list.
65 The actual body of the list item will be indented by this much
66 \e{plus} the value configured by \cw{\\cfg\{text-listitem-indent\}}.
68 \dt \I{\cw{\\cfg\{text-listitem-indent\}}}\cw{\\cfg\{text-listitem-indent\}\{}\e{indent}\cw{\}}
70 \dd Specifies how many extra spaces should be used to indent the
71 body of a list item, over and above the number configured in
72 \cw{\\cfg\{text-list-indent\}}.
74 \dt \I{\cw{\\cfg\{text-indent-preamble\}}}\cw{\\cfg\{text-indent-preamble\}\{}\e{boolean}\cw{\}}
76 \dd When this is set to \c{true}, the document \i{preamble} (i.e. any
77 paragraphs appearing before the first chapter heading) will be
78 indented to the level specified by \cw{\\cfg\{text-indent\}}. If
79 this setting is \c{false}, the document preamble will not be
80 indented at all from the left margin.
82 \S{output-text-headings} \ii{Configuring heading display}
84 The directives in this section allow you to configure the appearance
85 of the title, chapter and section headings in your text file.
87 Several of the directives listed below specify the \i{alignment} of
88 a heading. These alignment options have three possible values:
92 \dd Align the heading to the very left of the text file (column zero).
96 \dd Align the section title to the left of the main display region
97 (in other words, indented to the level specified by
98 \cw{\\cfg\{text-indent\}}). The section \e{number} is placed to the
99 left of that (so that it goes in the margin if there is room).
103 \dd Centre the heading.
105 Also, several of the directives below specify how a title should be
106 \I{underlining}underlined. The parameter to one of these directives
107 should be either blank (\cw{\{\}}) or a piece of text which will be
108 repeated to produce the underline. So you might want to specify, for
109 example, \cw{\\text-title-underline\{=\}} but
110 \cw{\\text-chapter-underline\{\-\}}.
112 You can also specify more than one underline setting, and Halibut
113 will choose the first one that the output character set supports.
114 So, for example, you could write
115 \cw{\\text-chapter-underline\{\\u203e\}\{\-\}}, and Halibut would use
116 the Unicode \q{OVERLINE} character where possible and fall back to
117 the ASCII minus sign otherwise.
119 \dt \I{\cw{\\cfg\{text-title-align\}}}\cw{\\cfg\{text-title-align\}\{}\e{alignment}\cw{\}}
121 \dd Specifies the alignment of the overall document title: \c{left},
122 \c{leftplus} or \c{centre}.
124 \dt \I{\cw{\\cfg\{text-title-underline\}}}\cw{\\cfg\{text-title-underline\}\{}\e{underline-text}\cw{\}}
126 \dd Specifies how the overall document title should be underlined.
128 \dt \I{\cw{\\cfg\{text-chapter-align\}}}\cw{\\cfg\{text-chapter-align\}\{}\e{alignment}\cw{\}}
130 \dd Specifies the alignment of chapter and appendix headings.
132 \dt \I{\cw{\\cfg\{text-chapter-underline\}}}\cw{\\cfg\{text-chapter-underline\}\{}\e{underline-text}\cw{\}}
134 \dd Specifies how chapter and appendix headings should be underlined.
136 \dt \I{\cw{\\cfg\{text-chapter-numeric\}}}\cw{\\cfg\{text-chapter-numeric\}\{}\e{boolean}\cw{\}}
138 \dd If this is set to \c{true}, then chapter headings will not
139 contain the word \q{Chapter} (or whatever other word you have
140 defined in its place - see \k{input-sections} and \k{input-config});
141 they will just contain the chapter \e{number}, followed by the
142 chapter title. If you set this to \c{false}, chapter headings will
143 be prefixed by \q{Chapter} or equivalent.
145 \dt \I{\cw{\\cfg\{text-chapter-suffix\}}}\cw{\\cfg\{text-chapter-suffix\}\{}\e{text}\cw{\}}
147 \dd This specifies the suffix text to be appended to the chapter
148 number, before displaying the chapter title. For example, if you set
149 this to \cq{:\_}, then the chapter title might look something
150 like \q{Chapter 2: Doing Things}.
152 \dt \I{\cw{\\cfg\{text-section-align\}}}\cw{\\cfg\{text-section-align\}\{}\e{level}\cw{\}\{}\e{alignment}\cw{\}}
154 \dd Specifies the alignment of section headings at a particular
155 level. The \e{level} parameter specifies which level of section
156 headings you want to affect: 0 means first-level headings (\c{\\H}),
157 1 means second-level headings (\c{\\S}), 2 means the level below
158 that (\c{\\S2}), and so on. The \e{alignment} parameter is treated
159 just like the other alignment directives listed above.
161 \dt \I{\cw{\\cfg\{text-section-underline\}}}\cw{\\cfg\{text-section-underline\}\{}\e{level}\cw{\}\{}\e{underline-text}\cw{\}}
163 \dd Specifies how to underline section headings at a particular level.
165 \dt \I{\cw{\\cfg\{text-section-numeric\}}}\cw{\\cfg\{text-section-numeric\}\{}\e{level}\cw{\}\{}\e{boolean}\cw{\}}
167 \dd Specifies whether section headings at a particular level should
168 contain the word \q{Section} or equivalent (if \c{false}), or should
169 be numeric only (if \c{true}).
171 \dt \I{\cw{\\cfg\{text-section-suffix\}}}\cw{\\cfg\{text-section-suffix\}\{}\e{level}\cw{\}\{}\e{text}\cw{\}}
173 \dd Specifies the \I{suffix text, in section titles}suffix text to
174 be appended to section numbers at a particular level, before
175 displaying the section title.
177 \S{output-text-characters} Configuring the characters used
179 \dt \I\cw{\\cfg\{text-charset\}}\cw{\\cfg\{text-charset\}\{}\e{character set name}\cw{\}}
181 \dd This tells Halibut what \i{character set} the output should be
182 in. Any Unicode characters representable in this set will be output
183 verbatim; any other characters will not be output and their
184 \i{fallback text} (if any) will be used instead.
188 The character set names are the same as for
189 \cw{\\cfg\{input-charset\}} (see \k{input-config}). However, unlike
190 \cw{\\cfg\{input-charset\}}, this directive affects the \e{entire}
191 output; it's not possible to switch encodings halfway through.
195 \dt \I{\cw{\\cfg\{text-bullet\}}}\cw{\\cfg\{text-bullet\}\{}\e{text}\cw{\}}[\cw{\{}\e{text}...\cw{\}}]
197 \dd This specifies the text which should be used as the \i{bullet}
198 in bulletted lists. It can be one character
199 (\cw{\\cfg\{text-bullet\}\{-\}}), or more than one
200 (\cw{\\cfg\{text-bullet\}\{(*)\}}).
204 Like \cw{\\cfg\{quotes\}} (see \k{input-config}), you can specify multiple
205 possible options after this command, and Halibut will choose the first one
206 which the output character set supports. For example, you might write
207 \cw{\\cfg\{text-bullet\}\{\\u2022\}\{\\u00b7\}\{*\}}, in which case
208 Halibut would use the Unicode \q{BULLET} character where possible,
209 fall back to the ISO-8859-1 \q{MIDDLE DOT} if that wasn't available,
210 and resort to the ASCII asterisk if all else failed.
214 \dt \I{\cw{\\cfg\{text-rule\}}}\cw{\\cfg\{text-rule\}\{}\e{text}\cw{\}}[\cw{\{}\e{text}...\cw{\}}]
216 \dd This specifies the text which should be used for drawing
217 \i{horizontal rules} (generated by \i\c{\\rule}; see
218 \k{input-rule}). It can be one character, or more than one. The
219 string you specify will be repeated to reach the required width, so
220 you can specify something like \cq{-=} to get a rule that looks
225 Like \cw{\\cfg\{text-bullet\}}, you can specify multiple fallback
226 options in this command.
230 \dt \I{\cw{\\cfg\{text-quotes\}}}\cw{\\cfg\{text-quotes\}\{}\e{open-quote}\cw{\}\{}\e{close-quote}\cw{\}}[\cw{\{}\e{open-quote}\cw{\}\{}\e{close-quote}...\cw{\}}]
232 \dd This specifies a set of quote characters for the text backend,
233 overriding any defined by \cw{\\cfg\{quotes\}}. It has the same syntax
234 (see \k{input-config}).
238 In this backend, these quotes will also be used to mark text enclosed
239 in the \c{\\c} command (see \k{input-code}).
243 \dt \I{\cw{\\cfg\{text-emphasis\}}}\cw{\\cfg\{text-emphasis\}\{}\e{start-emph}\cw{\}\{}\e{end-emph}\cw{\}}[\cw{\{}\e{start-emph}\cw{\}\{}\e{end-emph}...\cw{\}}]
245 \dd This specifies the characters which should be used to surround
246 emphasised text (written using the \c{\\e} command; see
251 You should separately specify the start-emphasis and end-emphasis
252 text, each of which can be more than one character if you want.
253 Also, like \cw{\\cfg\{text-quotes\}}, you can specify multiple pairs
254 of fallback options in this command, and Halibut will always use a
259 \S{output-text-misc} Miscellaneous configuration options
261 \dt \I{\cw{\\cfg\{text-list-suffix\}}}\cw{\\cfg\{text-list-suffix\}\{}\e{text}\cw{\}}
263 \dd This text is appended to the number on a \i{numbered list} item
264 (see \k{input-list-number}). So if you want to label your lists as
265 \q{1)}, \q{2)} and so on, then you would write
266 \cw{\\cfg\{text-list-suffix\}\{)\}}.
268 \dt \I{\cw{\\cfg\{text-versionid\}}}\cw{\\cfg\{text-versionid\}\{}\e{boolean}\cw{\}}
270 \dd If this is set to \c{true}, \i{version ID paragraphs} (defined
271 using the \i\c{\\versionid} command - see \k{input-blurb}) will be
272 included at the bottom of the text file. If it is set to \c{false},
273 they will be omitted completely.
275 \# FIXME: code indentation is configurable, therefore \quote
276 \# indentation probably ought to be as well.
278 \# FIXME: text-indent-* should be consistently named.
280 \S{output-text-defaults} Default settings
282 The \i{default settings} for Halibut's plain text output format are:
284 \c \cfg{text-filename}{output.txt}
286 \c \cfg{text-width}{68}
287 \c \cfg{text-indent}{7}
288 \c \cfg{text-indent-code}{2}
289 \c \cfg{text-list-indent}{1}
290 \c \cfg{text-listitem-indent}{3}
291 \c \cfg{text-indent-preamble}{false}
293 \c \cfg{text-title-align}{centre}
294 \c \cfg{text-title-underline}{\u2550}{=}
296 \c \cfg{text-chapter-align}{left}
297 \c \cfg{text-chapter-underline}{\u203e}{-}
298 \c \cfg{text-chapter-numeric}{false}
299 \c \cfg{text-chapter-suffix}{: }
301 \c \cfg{text-section-align}{0}{leftplus}
302 \c \cfg{text-section-underline}{0}{}
303 \c \cfg{text-section-numeric}{0}{true}
304 \c \cfg{text-section-suffix}{0}{ }
306 \c \cfg{text-section-align}{1}{leftplus}
307 \c \cfg{text-section-underline}{1}{}
308 \c \cfg{text-section-numeric}{1}{true}
309 \c \cfg{text-section-suffix}{1}{ }
311 \c ... and so on for all section levels below this ...
312 \e iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
314 \c \cfg{text-charset}{ASCII}
315 \c \cfg{text-bullet}{\u2022}{-}
316 \c \cfg{text-rule}{\u2500}{-}
317 \c \cfg{text-quotes}{\u2018}{\u2019}{`}{'}
318 \c \cfg{text-emphasis}{_}{_}
320 \c \cfg{text-list-suffix}{.}
321 \c \cfg{text-versionid}{true}
325 This output format generates an \i{HTML} version of the document. By
326 default, this will be in multiple files, starting with
327 \c{Contents.html} and splitting the document into files by chapter
328 and/or subsection. You can configure precisely how the text is split
329 between HTML files using the configuration commands described in
330 this section. In particular, you can configure Halibut to output one
331 single HTML file instead of multiple ones.
333 \I{\cw{\\cfg\{xhtml-anything\}}}Configuration directives with an
334 \c{xhtml-} prefix are synonyms for those with an \c{html-} prefix.
336 \S{output-html-file} Controlling the output file names
338 \dt \I{\cw{\\cfg\{html-contents-filename\}}}\cw{\\cfg\{html-contents-filename\}\{}\e{filename}\cw{\}}
340 \dd Sets the \i{output file name} in which to store the top-level
341 contents page. Since this is the first page a user ought to see when
342 beginning to read the document, a good choice in many cases might be
343 \c{index.html} (although this is not the default, for historical
346 \dt \I{\cw{\\cfg\{html-index-filename\}}}\cw{\\cfg\{html-index-filename\}\{}\e{filename}\cw{\}}
348 \dd Sets the file name in which to store the document's index.
350 \dt \I{\cw{\\cfg\{html-template-filename\}}}\cw{\\cfg\{html-template-filename\}\{}\e{template}\cw{\}}
352 \dd Provides a \i{template} to be used when constructing the file
353 names of each chapter or section of the document. This template
354 should contain at least one \i\e{formatting command}, in the form of
355 a per cent sign followed by a letter. (If you need a literal per
356 cent sign, you can write \c{%%}.)
360 The formatting commands used in this template are:
362 \dt \I{%N-upper}\c{%N}
364 \dd Expands to the visible title of the section, with white space
365 removed. So in a chapter declared as \cq{\\C\{fish\} Catching
366 Fish}, this formatting command would expand to
371 \dd Expands to the type and number of the section, without white
372 space. So in chapter 1 this would expand to \cq{Chapter1}; in
373 section A.4.3 it would expand to \cq{SectionA.4.3}, and so on.
374 If the section has no number (an unnumbered chapter created using
375 \c{\\U}), this directive falls back to doing the same thing as
380 \dd Expands to the number of the section, in a format suitable for an
381 HTML fragment name. The first character of the section type is
382 prepended to the section number. So in chapter 1 this would expand to
383 \cq{C1}; in section A.4.3 it would expand to \cq{SA.4.3}, and so on.
384 If the section has no number (an unnumbered chapter created using
385 \c{\\U}), this directive falls back to doing the same thing as \c{%N}.
389 \dd Expands to the internal keyword specified in the section title.
390 So in a chapter declared as \cq{\\C\{fish\} Catching Fish}, this
391 formatting command would expand to \cq{fish}. If the section has
392 no keyword (an unnumbered chapter created using \c{\\U}), this
393 directive falls back to doing the same thing as \c{%N}.
395 These formatting directives can also be used in the
396 \cw{\\cfg\{html-template-fragment\}} configuration directive (see
397 \k{output-html-misc}).
401 \dt \I{\cw{\\cfg\{html-single-filename\}}}\cw{\\cfg\{html-single-filename\}\{}\e{filename}\cw{\}}
403 \dd Sets the file name in which to store the entire document, if
404 Halibut is configured (using \c{\\cfg\{html-leaf-level\}\{0\}} to
405 produce a single self-contained file. Both this directive \e{and}
406 \c{\\cfg\{html-leaf-level\}\{0\}} are implicitly generated if you
407 provide a file name parameter after the command-line option
408 \i\c{--html} (see \k{running-options}).
410 \S{output-html-split} Controlling the splitting into HTML files
412 By default, the HTML output from Halibut is split into multiple
413 files. Each file typically contains a single chapter or section and
414 everything below it, unless subsections of that chapter are
415 themselves split off into further files.
417 Most files also contain a contents section, giving hyperlinks to the
418 sections in the file and/or the sections below it.
420 The configuration directives listed below allow you to configure the
421 splitting into files, and the details of the contents sections.
423 \dt \I{\cw{\\cfg\{html-leaf-level\}}}\cw{\\cfg\{html-leaf-level\}\{}\e{depth}\cw{\}}
425 \dd This setting indicates the depth of section which should be
426 given a \I{leaf file}\q{leaf} file (a file with no sub-files). So if
427 you set it to 1, for example, then every chapter will be given its
428 own HTML file, plus a top-level \i{contents file}. If you set this
429 to 2, then each chapter \e{and} each \c{\\H} section will have a
430 file, and the chapter files will mostly just contain links to their
435 If you set this option to zero, then the whole document will appear
436 in a single file. If you do this, Halibut will call that file
437 \i\c{Manual.html} instead of \i\c{Contents.html} by default.
439 This option is automatically set to zero if you provide a file name
440 parameter after the command-line option \i\c{--html} (see
441 \k{running-options}), because you have specified a single file name
442 and so Halibut assumes you want the whole document to be placed in
445 You can also specify the special name \c{infinity} (or \c{infinite}
446 or \c{inf}) if you want to ensure that \e{every} section and
447 subsection ends up in a separate file no matter how deep you go.
451 \dt \I{\cw{\\cfg\{html-contents-depth\}}}\cw{\\cfg\{html-contents-depth\}\{}\e{level}\cw{\}\{}\e{depth}\cw{\}}
453 \dd This directive allows you to specify how \I{depth of
454 contents}deep any contents section in a particular level of file
459 The \e{level} parameter indicates which level of contents section
460 you are dealing with. 0 denotes the main contents section in the
461 topmost file \c{Contents.html}; 1 denotes a contents section in a
462 chapter file; 2 is a contents section in a file containing a \c{\\H}
465 The \e{depth} parameter indicates the maximum depth of heading which
466 will be shown in this contents section. Again, 1 denotes a chapter,
467 2 is a \c{\\H} heading, 3 is a \c{\\S} heading, and so on.
469 So, for example: \cw{\\cfg\{html-contents-depth\}\{1\}\{3\}} instructs
470 Halibut to put contents links in chapter files for all sections down
471 to \c{\\S} level, but not to go into any more detail than that.
473 For backwards compatibility, the alternative syntax
474 \cw{\\cfg\{html-contents-depth-}\e{level}\cw{\}\{}\e{depth}\cw{\}}
479 \dt \I{\cw{\\cfg\{html-leaf-contains-contents\}}}\cw{\\cfg\{html-leaf-contains-contents\}\{}\e{boolean}\cw{\}}
481 \dd If you set this to \c{true}, then each leaf file will contain
482 its own contents section which summarises the text within it.
484 \dt \I{\cw{\\cfg\{html-leaf-smallest-contents\}}}\cw{\\cfg\{html-leaf-smallest-contents\}\{}\e{number}\cw{\}}
486 \dd Contents sections in leaf files are not output at all if they
487 contain very few entries (on the assumption that it just isn't worth
488 bothering). This directive configures the minimum number of entries
489 required in a leaf contents section to make Halibut bother
490 generating it at all.
492 \S{output-html-html} Including pieces of your own HTML
494 The directives in this section allow you to supply pieces of
495 \I{HTML}\i{verbatim HTML} code, which will be included in various
496 parts of the output files.
498 Note that none of Halibut's usual character set translation is applied
499 to this code; it is assumed to already be in a suitable encoding for
500 the target HTML files.
502 \dt \I{\cw{\\cfg\{html-head-end\}}}\cw{\\cfg\{html-head-end\}\{}\e{HTML text}\cw{\}}
504 \dd The text you provide in this directive is placed at the end of
505 the \i\cw{<HEAD>} section of each output HTML file. So this is a
506 good place to put, for example, a link to a \i{CSS} \i{stylesheet}.
508 \dt \I{\cw{\\cfg\{html-local-head\}}}\cw{\\cfg\{html-local-head\}\{}\e{HTML text}\cw{\}}
510 \dd This configuration directive is local: you specify it within a
511 document section, and it acts on that section only.
515 The text you provide in this directive is placed at the end of the
516 \i\cw{<HEAD>} section of whichever output HTML file contains the
517 section in which the directive was placed. You can specify this
518 directive multiple times in multiple sections if you like.
520 This directive is particularly useful for constructing \i{MacOS
521 on-line help}, which is mostly normal HTML but which requires a
522 special \i\cw{<META NAME="AppleTitle">} tag in the topmost source
523 file. You can arrange this by placing this configuration directive
524 in the preamble or the introduction section, something like this:
526 \c \cfg{html-local-head}{<meta name="AppleTitle"
527 \c content="MyApp Help">}
531 \dt \I{\cw{\\cfg\{html-body-tag\}}}\cw{\\cfg\{html-body-tag\}\{}\e{HTML text}\cw{\}}
533 \dd The text you provide in this directive is used in place of the
534 \i\cw{<BODY>} tag in each output file. So if you wanted to define a
535 \i{background colour}, for example, you could write
536 \cw{\\cfg\{html-body-tag\}\{<body bg="#123456">\}}.
538 \dt \I{\cw{\\cfg\{html-body-start\}}}\cw{\\cfg\{html-body-start\}\{}\e{HTML text}\cw{\}}
540 \dd The text you provide in this directive is placed at the
541 beginning of the \i\cw{<BODY>} section of each output HTML file. So
542 if you intend your HTML files to be part of a web site with a
543 standard \i{house style}, and the style needs a \i{header} at the
544 top of every page, this is where you can add that header.
546 \dt \I{\cw{\\cfg\{html-body-end\}}}\cw{\\cfg\{html-body-end\}\{}\e{HTML text}\cw{\}}
548 \dd The text you provide in this directive is placed at the end of
549 the \i\cw{<BODY>} section of each output HTML file, before any address
550 section. So if you intend your HTML files to be part of a web site
551 with a standard \i{house style}, and the style needs a \i{footer} at
552 the bottom of every page, this is where you can add that footer.
554 \dt \I{\cw{\\cfg\{html-address-start\}}}\cw{\\cfg\{html-address-start\}\{}\e{HTML text}\cw{\}}
556 \dd The text you provide in this directive is placed at the
557 beginning of the \i\cw{<ADDRESS>} section at the bottom of each
558 output HTML file. This might be a good place to put authors'
559 \i{contact details}, for example.
561 \dt \I{\cw{\\cfg\{html-address-end\}}}\cw{\\cfg\{html-address-end\}\{}\e{HTML text}\cw{\}}
563 \dd The text you provide in this directive is placed at the end of
564 the \i\cw{<ADDRESS>} section at the bottom of each output HTML file,
565 after the version IDs (if present).
567 \dt \I{\cw{\\cfg\{html-navigation-attributes\}}}\cw{\\cfg\{html-navigation-attributes\}\{}\e{HTML attributes}\cw{\}}
569 \dd The text you provide in this directive is included inside the
570 \cw{<P>} tag containing the \i{navigation links} at the top of each
571 page (\i{\q{Previous}} / \i{\q{Contents}} / \i{\q{Next}}). So if you
572 wanted the navigation links to have a particular CSS style, you
574 \cw{\\cfg\{html-navigation-attributes\}\{class="foo"\}}, and the
575 navigation-links paragraph would then begin with the tag \cw{<p
578 \S{output-html-headings} \ii{Configuring heading display}
580 \dt \I{\cw{\\cfg\{html-chapter-numeric\}}}\cw{\\cfg\{html-chapter-numeric\}\{}\e{boolean}\cw{\}}
582 \dd If this is set to \c{true}, then chapter headings will not
583 contain the word \q{Chapter} (or whatever other word you have
584 defined in its place - see \k{input-sections} and \k{input-config});
585 they will just contain the chapter \e{number}, followed by the
586 chapter title. If you set this to \c{false}, chapter headings will
587 be prefixed by \q{Chapter} or equivalent.
589 \dt \I{\cw{\\cfg\{html-chapter-suffix\}}}\cw{\\cfg\{html-chapter-suffix\}\{}\e{text}\cw{\}}
591 \dd This specifies the suffix text to be appended to the chapter
592 number, before displaying the chapter title. For example, if you set
593 this to \cq{:\_}, then the chapter title might look something
594 like \q{Chapter 2: Doing Things}.
596 \dt \I{\cw{\\cfg\{html-section-numeric\}}}\cw{\\cfg\{html-section-numeric\}\{}\e{level}\cw{\}\{}\e{boolean}\cw{\}}
598 \# {level} can be omitted (defaults to 0). Is this intentional?
600 \dd Specifies whether section headings at a particular level should
601 contain the word \q{Section} or equivalent (if \c{false}), or should
602 be numeric only (if \c{true}). The \e{level} parameter specifies
603 which level of section headings you want to affect: 0 means
604 first-level headings (\c{\\H}), 1 means second-level headings
605 (\c{\\S}), 2 means the level below that (\c{\\S2}), and so on.
607 \dt \I{\cw{\\cfg\{html-section-suffix\}}}\cw{\\cfg\{html-section-suffix\}\{}\e{level}\cw{\}\{}\e{text}\cw{\}}
609 \# {level} can be omitted (defaults to 0). Is this intentional?
611 \dd Specifies the suffix text to be appended to section numbers at a
612 particular level, before displaying the section title.
614 \S{output-html-names} Configuring standard text
616 These directives let you fine-tune the names Halibut uses in places
617 such as the navigation bar to refer to various parts of the document,
618 and other standard pieces of text, for instance to change them to a
621 \dt \I{\cw{\\cfg\{html-preamble-text\}}}\cw{\\cfg\{html-preamble-text\}\{}\e{text}\cw{\}}
623 \dt \I{\cw{\\cfg\{html-contents-text\}}}\cw{\\cfg\{html-contents-text\}\{}\e{text}\cw{\}}
625 \dt \I{\cw{\\cfg\{html-index-text\}}}\cw{\\cfg\{html-index-text\}\{}\e{text}\cw{\}}
627 \dd Text used to refer to the preamble (i.e., any paragraphs before
628 the first chapter heading), contents, and index respectively, in the
629 navigation bar, contents, and index.
633 (\c{html-contents-text} and \c{html-index-text} override the
634 cross-format configuration keywords \c{contents} and \c{index} (see
635 \k{input-config}, if both appear. They are legacy keywords preserved
636 for backwards compatibility; you should generally use \c{contents}
641 \dt \I{\cw{\\cfg\{html-title-separator\}}}\cw{\\cfg\{html-title-separator\}\{}\e{text}\cw{\}}
643 \dd If multiple headings are used in a file's \cw{<TITLE>} tag, this
644 text is used to separate them.
646 \# Under what circumstances can this occur?
648 \dt \I{\cw{\\cfg\{html-index-main-separator\}}}\cw{\\cfg\{html-index-main-separator\}\{}\e{text}\cw{\}}
650 \dd Separator between index term and references in the index.
652 \dt \I{\cw{\\cfg\{html-index-multiple-separator\}}}\cw{\\cfg\{html-index-multiple-separator\}\{}\e{text}\cw{\}}
654 \dd Separator between multiple references for a single index term in
657 \dt \I{\cw{\\cfg\{html-pre-versionid\}}}\cw{\\cfg\{html-pre-versionid\}\{}\e{text}\cw{\}}
659 \dt \I{\cw{\\cfg\{html-post-versionid\}}}\cw{\\cfg\{html-post-versionid\}\{}\e{text}\cw{\}}
661 \dd Text surrounding each output \i{version ID paragraph}.
663 \dt \I{\cw{\\cfg\{html-nav-prev-text\}}}\cw{\\cfg\{html-nav-prev-text\}\{}\e{text}\cw{\}}
665 \dt \I{\cw{\\cfg\{html-nav-next-text\}}}\cw{\\cfg\{html-nav-next-text\}\{}\e{text}\cw{\}}
667 \dd The text used for the \q{previous page} and \q{next page} links on
670 \dt \I{\cw{\\cfg\{html-nav-separator\}}}\cw{\\cfg\{html-nav-separator\}\{}\e{text}\cw{\}}
672 \dd Separator between links in the navigation bar.
674 \S{output-html-characters} Configuring the characters used
676 Unlike the other backends, HTML does not have a single
677 \i\cw{\\cfg\{html-charset\}} directive, as there are several levels of
678 character encoding to consider.
680 The character set names are the same as for
681 \cw{\\cfg\{input-charset\}} (see \k{input-config}). However, unlike
682 \cw{\\cfg\{input-charset\}}, these directives affect the \e{entire}
683 output; it's not possible to switch encodings halfway through.
685 \dt \I\cw{\\cfg\{html-output-charset\}}\cw{\\cfg\{html-output-charset\}\{}\e{character set name}\cw{\}}
687 \dd The character encoding of the HTML file to be output. Unicode
688 characters in this encoding's repertoire are included literally rather
689 than as \i{HTML entities}.
691 \dt \I\cw{\\cfg\{html-restrict-charset\}}\cw{\\cfg\{html-restrict-charset\}\{}\e{character set name}\cw{\}}
693 \dd Only Unicode characters representable in this character set will be
694 output; any others will be omitted and use their fallback text, if
695 any. Characters not in \q{html-output-charset} will be represented as
696 HTML numeric entities.
698 \dt \I{\cw{\\cfg\{html-quotes\}}}\cw{\\cfg\{html-quotes\}\{}\e{open-quote}\cw{\}\{}\e{close-quote}\cw{\}}[\cw{\{}\e{open-quote}\cw{\}\{}\e{close-quote}...\cw{\}}]
700 \dd Specifies the quotation marks to use, overriding any
701 \cw{\\cfg\{quotes\}} directive. You can specify multiple
702 fallback options. Works exactly like the \cw{\\cfg\{text-quotes\}}
703 directive (see \k{output-text-characters}).
705 \S{output-html-misc} Miscellaneous options
707 \dt \I\cw{\\cfg\{html-version\}}\cw{\\cfg\{html-version\}\{}\e{version}\cw{\}}
709 \dd Identifies the precise version of HTML that is output. This
710 affects the declaration within the HTML, and also has minor effects on
711 the body of the HTML so that it is valid for the declared version. The
712 available variants are:
722 \dd W3C HTML 4.01 Strict
726 \dd ISO/IEC 15445:2000
728 \dt \cw{xhtml1.0transitional}
730 \dd W3C XHTML 1.0 Transitional
732 \dt \cw{xhtml1.0strict}
734 \dd W3C XHTML 1.0 Strict
738 \dt \I{\cw{\\cfg\{html-template-fragment\}}}\cw{\\cfg\{html-template-fragment\}\{}\e{template}\cw{\}}[\cw{\{}\e{template}\cw{\}\{}...\cw{\}}]
740 \dd This directive lets you specify a \i{template}, with exactly the
741 same syntax used in \cw{\\cfg\{html-template-filename\}} (see
742 \k{output-html-file}), to be used for the anchor names (\i\cw{<A
743 NAME="...">}) used to allow URLs to refer to specific sections
744 within a particular HTML file. So if you set this to \cq{%k},
745 for example, then each individual section in your document will be
746 addressable by means of a URL ending in a \c{#} followed by your
747 internal section keyword.
751 If more than one template is specified, anchors are generated in all
752 the specified formats; Halibut's own cross-references are generated
753 with the first template.
755 Characters that are not permitted in anchor names are stripped. If
756 there are no valid characters left, or a fragment is non-unique,
757 Halibut starts inventing fragment names and suffixes as appropriate.
759 Note that there are potentially fragment names that are not controlled
760 by this mechanism, such as index references.
764 \dt \I{\cw{\\cfg\{html-versionid\}}}\cw{\\cfg\{html-versionid\}\{}\e{boolean}\cw{\}}
766 \dd If this is set to \c{true}, \i{version ID paragraphs} (defined using
767 the \i\c{\\versionid} command - see \k{input-blurb}) will be included
768 visibly in the \i\cw{<ADDRESS>} section at the bottom of each HTML
769 file. If it is set to \c{false}, they will only be included as HTML
772 \dt \I{\cw{\\cfg\{html-rellinks\}}}\cw{\\cfg\{html-rellinks\}\{}\e{boolean}\cw{\}}
774 \dd If this is set to \c{true}, machine-readable relational links will
775 be emitted in each HTML file (\I{\cw{<LINK>} tags}\cw{<LINK
776 REL="}\e{next}\cw{">} and so on within the \i\cw{<HEAD>} section)
777 providing links to related files. The same set of links are provided
778 as in the navigation bar (with which this should not be confused).
782 Some browsers make use of this semantic information, for instance to
783 allow easy navigation through related pages, and to prefetch the next
784 page. (Search engines can also make use of it.) However, many browsers
785 ignore this markup, so it would be unwise to rely on it for
788 The use and rendering of this information is entirely up to the
789 browser; none of the other Halibut options for the navigation bar will
794 \dt \I{\cw{\\cfg\{html-suppress-navlinks\}}}\cw{\\cfg\{html-suppress-navlinks\}\{}\e{boolean}\cw{\}}
796 \dd If this is set to \c{true}, the usual \i{navigation links} within
797 the \e{body} of each HTML file (near the top of the rendered page) will
800 \dt \I{\cw{\\cfg\{html-suppress-address\}}}\cw{\\cfg\{html-suppress-address\}\{}\e{boolean}\cw{\}}
802 \dd If this is set to \c{true}, the \i\cw{<ADDRESS>} section at the
803 bottom of each HTML file will be omitted completely. (This will
804 therefore also cause \i{version IDs} not to be included visibly.)
806 \dt \I{\cw{\\cfg\{html-author\}}}\cw{\\cfg\{html-author\}\{}\e{text}\cw{\}}
808 \dd The text supplied here goes in a \I{\cw{<META>} tags}\cw{<META
809 name="author">} tag in the output HTML files, so that browsers which
810 support this can automatically identify the \i{author} of the document.
812 \dt \I{\cw{\\cfg\{html-description\}}}\cw{\\cfg\{html-description\}\{}\e{text}\cw{\}}
814 \dd The text supplied here goes in a \I{\cw{<META>} tags}\cw{<META
815 name="description">} tag in the output HTML files, so that browsers
816 which support this can easily pick out a brief \I{description, of
817 document}description of the document.
819 \S{output-html-mshtmlhelp} Generating MS Windows \i{HTML Help}
821 The HTML files output from Halibut's HTML back end can be used as
822 input to the MS Windows HTML Help compiler. In order to do this, you
823 also need some auxiliary files: a project file, and (probably) a
824 contents file and an index file. Halibut can optionally generate
827 To enable the generation of MS HTML Help auxiliary files, use the
828 following configuration directives:
830 \dt \I\cw{\\cfg\{html-mshtmlhelp-project\}}\cw{\\cfg\{html-mshtmlhelp-project\}\{}\e{filename}\cw{\}}
832 \dd Instructs Halibut to output an HTML Help project file with the
833 specified name. You will almost certainly want the filename to end
834 in the extension \c{.hhp} (although Halibut will not enforce this).
835 If you use this option, you must also use the
836 \cw{html-mshtmlhelp-chm} option to specify the desired name of the
839 \dt \I\cw{\\cfg\{html-mshtmlhelp-chm\}}\cw{\\cfg\{html-mshtmlhelp-chm\}\{}\e{filename}\cw{\}}
841 \dd Specifies the desired name of the compiled HTML Help file. You
842 will almost certainly want this to have the extension \c{.chm}
843 (although Halibut will not enforce this). The name you specify here
844 will be written into the help project file. If you specify this
845 option, you must also use the \cw{html-mshtmlhelp-project} option to
846 request a help project file in the first place.
848 \dt \I\cw{\\cfg\{html-mshtmlhelp-contents\}}\cw{\\cfg\{html-mshtmlhelp-contents\}\{}\e{filename}\cw{\}}
850 \dd Instructs Halibut to output an HTML Help contents file with the
851 specified name, and refer to it in the help project file. You will
852 almost certainly want the filename to end in the extension \c{.hhc}
853 (although Halibut will not enforce this). This option will be
854 ignored if you have not also specified a help project file.
858 Creating a contents file like this causes the HTML Help viewer to
859 display a contents tree in the pane to the left of the main text
860 window. You can choose to generate an HTML Help project without this
861 feature, in which case the user will still be able to navigate
862 around the document by using the ordinary internal links in the HTML
863 files themselves just as if it were a web page. However, using a
864 contents file is recommended.
868 \dt \I\cw{\\cfg\{html-mshtmlhelp-index\}}\cw{\\cfg\{html-mshtmlhelp-index\}\{}\e{filename}\cw{\}}
870 \dd Instructs Halibut to output an HTML Help index file with the
871 specified name, and refer to it in the help project file. You will
872 almost certainly want the filename to end in the extension \c{.hhk}
873 (although Halibut will not enforce this). This option will be
874 ignored if you have not also specified a help project file.
878 Specifying this option suppresses the generation of an HTML-based
879 index file (see \cw{\\cfg\{html-index-filename\}} in
880 \k{output-html-file}).
882 Creating an index file like this causes the HTML Help viewer to
883 provide a list of index terms in a pane to the left of the main text
884 window. You can choose to generate an HTML Help project without this
885 feature, in which case a conventional HTML index will be generated
886 instead (assuming you have any index terms at all defined) and the
887 user will still be able to use that. However, using an index file is
890 Halibut will not output an index file at all, or link to one from
891 the help project file, if your document contains no index entries.
895 If you use the above options, Halibut will output a help project
896 file which you should be able to feed straight to the command-line
897 MS HTML Help compiler (\cw{HHC.EXE}), or load into the MS HTML Help
898 Workshop (\cw{HHW.EXE}).
900 You may also wish to alter other HTML configuration options to make
901 the resulting help file look more like a help file and less like a
902 web page. A suggested set of additional configuration options for
903 HTML Help is as follows:
905 \b \cw{\\cfg\{html-leaf-level\}\{infinite\}}, because HTML Help
906 works best with lots of small files (\q{topics}) rather than a few
907 large ones. In particular, the contents and index mechanisms can
908 only reference files, not subsections within files.
910 \b \cw{\\cfg\{html-leaf-contains-contents\}\{false\}}, to suppress
911 the contents list above the main text of each bottom-level file.
913 \b \cw{\\cfg\{html-suppress-navlinks\}\{true\}}, because HTML Help
914 has its own navigation facilities and it looks a bit strange to
917 \b \cw{\\cfg\{html-suppress-address\}\{true\}}, because the
918 \cw{<ADDRESS>} section makes less sense in a help file than it does
921 \S{output-html-defaults} Default settings
923 The \i{default settings} for Halibut's HTML output format are:
925 \c \cfg{html-contents-filename}{Contents.html}
926 \c \cfg{html-index-filename}{IndexPage.html}
927 \c \cfg{html-template-filename}{%n.html}
928 \c \cfg{html-single-filename}{Manual.html}
930 \c \cfg{html-leaf-level}{2}
931 \c \cfg{html-leaf-contains-contents}{false}
932 \c \cfg{html-leaf-smallest-contents}{4}
933 \c \cfg{html-contents-depth}{0}{2}
934 \c \cfg{html-contents-depth}{1}{3}
935 \c ... and so on for all section levels below this ...
936 \e iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
938 \c \cfg{html-head-end}{}
939 \c \cfg{html-body-tag}{<body>}
940 \c \cfg{html-body-start}{}
941 \c \cfg{html-body-end}{}
942 \c \cfg{html-address-start}{}
943 \c \cfg{html-address-end}{}
944 \c \cfg{html-navigation-attributes}{}
946 \c \cfg{html-chapter-numeric}{false}
947 \c \cfg{html-chapter-suffix}{: }
949 \c \cfg{html-section-numeric}{0}{true}
950 \c \cfg{html-section-suffix}{0}{ }
952 \c \cfg{html-section-numeric}{1}{true}
953 \c \cfg{html-section-suffix}{1}{ }
955 \c ... and so on for all section levels below this ...
956 \e iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
958 \c \cfg{html-preamble-text}{Preamble}
959 \c \cfg{html-contents-text}{Contents}
960 \c \cfg{html-index-text}{Index}
961 \c \cfg{html-title-separator}{ - }
962 \c \cfg{html-index-main-separator}{: }
963 \c \cfg{html-index-multiple-separator}{, }
964 \c \cfg{html-pre-versionid}{[}
965 \c \cfg{html-post-versionid}{]}
966 \c \cfg{html-nav-prev-text}{Previous}
967 \c \cfg{html-nav-next-text}{Next}
968 \c \cfg{html-nav-separator}{ | }
970 \c \cfg{html-output-charset}{ASCII}
971 \c \cfg{html-restrict-charset}{UTF-8}
972 \c \cfg{html-quotes}{\u2018}{\u2019}{"}{"}
974 \c \cfg{html-version}{html4}
975 \c \cfg{html-template-fragment}{%b}
976 \c \cfg{html-versionid}{true}
977 \c \cfg{html-rellinks}{true}
978 \c \cfg{html-suppress-navlinks{false}
979 \c \cfg{html-suppress-address}{false}
980 \c \cfg{html-author}{}
981 \c \cfg{html-description}{}
983 \H{output-whlp} Windows Help
985 This output format generates data that can be used by the \i{Windows
986 Help} program \cw{WINHLP32.EXE}. There are two actual files
987 generated, one ending in \c{.hlp} and the other ending in \c{.cnt}.
989 Note that as of 2006, MS is discontinuing the Windows Help format in
990 favour of the newer HTML Help format (\c{.chm} files). Halibut is
991 not currently able to generate \c{.chm} files directly, but its HTML
992 back end can write out project files suitable for use as input to
993 the MS HTML Help compiler. See \k{output-html-mshtmlhelp} for more
996 Currently, the Windows Help output is hardcoded to be in the
997 \q{\i{Win1252}} character set. (If anyone knows how character sets
998 are encoded in Windows Help files, we'd appreciate help.)
1000 The Windows Help output format supports the following configuration
1003 \S{output-whlp-file} Output file name
1005 \dt \I{\cw{\\cfg\{winhelp-filename\}}}\cw{\\cfg\{winhelp-filename\}\{}\e{filename}\cw{\}}
1007 \dd Sets the \i{output file name} in which to store the man page.
1008 This directive is implicitly generated if you provide a file name
1009 parameter after the command-line option \i\c{--winhelp} (see
1010 \k{running-options}).
1014 Your output file name should end with \c{.hlp}; if it doesn't,
1015 Halibut will append it. Halibut will also generate a contents file
1016 (ending in \c{.cnt}) alongside the file name you specify.
1020 \S{output-whlp-characters} Configuring the characters used
1022 \dt \I{\cw{\\cfg\{winhelp-bullet\}}}\cw{\\cfg\{winhelp-bullet\}\{}\e{text}\cw{\}}[\cw{\{}\e{text}\cw{\}}...]
1024 \dd Specifies the text to use as the \i{bullet} in bulletted lists.
1025 You can specify multiple fallback options. Works exactly like the
1026 \cw{\\cfg\{text-bullet\}} directive (see
1027 \k{output-text-characters}).
1029 \dt \I{\cw{\\cfg\{winhelp-quotes\}}}\cw{\\cfg\{winhelp-quotes\}\{}\e{open-quote}\cw{\}\{}\e{close-quote}\cw{\}}[\cw{\{}\e{open-quote}\cw{\}\{}\e{close-quote}...\cw{\}}]
1031 \dd Specifies the quotation marks to use, overriding any
1032 \cw{\\cfg\{quotes\}} directive. You can specify multiple
1033 fallback options. Works exactly like the \cw{\\cfg\{text-quotes\}}
1034 directive (see \k{output-text-characters}).
1036 \S{output-whlp-misc} Miscellaneous configuration options
1038 \dt \I{\cw{\\cfg\{winhelp-contents-titlepage\}}}\cw{\\cfg\{winhelp-contents-titlepage\}\{}\e{title}\cw{\}}
1040 \dd Sets the text used to describe the help page containing the blurb
1041 (see \k{input-blurb}) and table of contents.
1044 \I{\cw{\\cfg\{winhelp-section-suffix\}}}\cw{\\cfg\{winhelp-section-suffix\}\{}\e{text}\cw{\}}
1046 \dd Specifies the \I{suffix text, in section titles}suffix text to
1047 be appended to section numbers, before displaying the section title.
1048 (Applies to all levels.)
1050 \dt \I{\cw{\\cfg\{winhelp-list-suffix\}}}\cw{\\cfg\{winhelp-list-suffix\}\{}\e{text}\cw{\}}
1052 \dd This text is appended to the number on a \i{numbered list} item,
1053 in exactly the same way as \cw{\\cfg\{text-list-suffix\}} (see
1054 \k{output-text-characters}).
1056 \dt \I{\cw{\\cfg\{winhelp-topic\}}}\cw{\\cfg\{winhelp-topic\}\{}\e{topic-name}\cw{\}}
1058 \dd This directive defines a Windows \i{Help topic} name in the current
1059 section. Topic names can be used by the program invoking
1060 \cw{WINHELP.EXE} to jump straight to a particular section. So you
1061 can use this for \i{context-sensitive help}.
1065 For example, if you used this directive in a particular section:
1067 \c \cfg{winhelp-topic}{savingfiles}
1069 then a Windows application could invoke Windows Help to jump to that
1070 particular section in the help file like this:
1072 \c WinHelp(hwnd, "mydoc.hlp", HELP_COMMAND,
1073 \c (DWORD)"JI(`',`savingfiles')");
1075 You can use this configuration directive many times, in many
1076 different subsections of your document, in order to define a lot of
1077 different help contexts which you can use in this way.
1081 \S{output-whlp-defaults} Default settings
1083 The \i{default settings} for the Windows Help output format are:
1085 \c \cfg{winhelp-filename}{output.hlp}
1087 \c \cfg{winhelp-bullet}{\u2022}{-}
1088 \c \cfg{winhelp-quotes}{\u2018}{\u2019}{"}{"}
1090 \c \cfg{winhelp-contents-titlepage}{Title page}
1091 \c \cfg{winhelp-section-suffix}{: }
1092 \c \cfg{winhelp-list-suffix}{.}
1094 and no \c{\\cfg\{winhelp-topic\}} directives anywhere.
1096 \H{output-man} Unix \cw{man} pages
1098 This output format generates a Unix \i{\cw{man} page}. That is to say,
1099 it generates \i\c{nroff} input designed to work with the \c{-mandoc}
1102 The available configuration options for this format are as follows:
1104 \S{output-man-file} Output file name
1106 \dt \I{\cw{\\cfg\{man-filename\}}}\cw{\\cfg\{man-filename\}\{}\e{filename}\cw{\}}
1108 \dd Sets the \i{output file name} in which to store the man page.
1109 This directive is implicitly generated if you provide a file name
1110 parameter after the command-line option \i\c{--man} (see
1111 \k{running-options}).
1113 \S{output-man-identity} Configuring headers and footers
1115 \dt \I{\cw{\\cfg\{man-identity\}}}\cw{\\cfg\{man-identity\}\{}\e{text}\cw{\}\{}\e{text...}\cw{\}}
1117 \dd This directive is used to generate the initial \i{\c{.TH}
1118 directive} that appears at the top of a \cw{man} page. It expects to
1119 be followed by some number of brace pairs containing text, which will
1120 be used in the \i{headers} and \i{footers} of the formatted output.
1124 A traditional order for the arguments appears to be:
1126 \n The name of the program.
1128 \n The (numeric) manual section.
1130 \n The date that the \cw{man} page was written.
1132 \n The name of any containing suite of which the program is a part.
1134 \n The name of the \i{author} of the \cw{man} page.
1136 For example, a typical \cw{man} page might contain
1138 \c \cfg{man-identity}{make-foo}{1}{June 2003}{foo-utils}{Fred
1143 \S{output-man-headings} Configuring heading display
1145 \dt \I{\cw{\\cfg\{man-headnumbers\}}}\cw{\\cfg\{man-headnumbers\}\{}\e{boolean}\cw{\}}
1147 \dd If this is set to \c{true}, then \i{section headings} in the
1148 \cw{man} page will have their \i{section numbers} displayed as usual. If
1149 set to \c{false}, the section numbers will be omitted. (\cw{man}
1150 pages traditionally have section names such as \q{SYNOPSIS},
1151 \q{OPTIONS} and \q{BUGS}, and do not typically number them, so
1152 \c{false} is the setting which conforms most closely to normal
1155 \dt \I{\cw{\\cfg\{man-mindepth\}}}\cw{\\cfg\{man-mindepth\}\{}\e{depth}\cw{\}}
1157 \dd If this is set to a number greater than 0, then section headings
1158 \e{higher} than the given depth will not be displayed. If it is set
1159 to zero, all section headings will be displayed as normal.
1163 The point of this is so that you can use the same Halibut input file
1164 to generate a quick-reference \cw{man} page for a program, \e{and} to
1165 include that \cw{man} page as an appendix in your program's full manual.
1166 If you are to include the \cw{man} page as an appendix, then the internal
1167 headings within the page will probably need to be at \c{\\H} or
1168 \c{\\S} level; therefore, when you format that input file on its own
1169 to create the \cw{man} page itself, you will need to have defined a
1170 \c{\\C} and possibly a \c{\\H} heading beforehand, which you don't
1171 want to see displayed.
1173 Here's an example. You might have a file \c{appendix.but}, which
1176 \c \A{manpages} \cw{man} pages for the Foo tool suite
1178 \c \cfg{man-mindepth}{2}
1180 Then you have a file \c{make-foo.but}, and probably others like it
1181 as well, each of which looks something like this:
1183 \c \cfg{man-identity}{make-foo}{1}{June 2003}{foo-utils}{Fred
1186 \c \H{man-foo} \cw{man} page for \c{make-foo}
1188 \c \S{man-foo-name} NAME
1190 \c \c{make-foo} - create Foo files for the Foo tool suite
1192 \c \S{man-foo-synopsis} SYNOPSIS
1194 \c ... and so on ...
1195 \e iiiiiiiiiiiiiiiii
1197 So when you're generating your main manual, you can include
1198 \c{appendix.but} followed by \c{make-foo.but} and any other \cw{man}
1199 pages you have, and your \cw{man} pages will be formatted neatly as
1200 part of an appendix. Then, in a separate run of Halibut, you can
1203 \c halibut appendix.but make-foo.but
1205 and this will generate a \cw{man} page \c{output.1}, in which the
1206 headings \q{\cw{man} pages for the Foo tool suite} and \q{\cw{man}
1207 page for \c{make-foo}} will not be displayed because of the
1208 \c{man-mindepth} directive. So the first visible heading in the
1209 output \cw{man} page will be \q{NAME}, exactly as a user would
1214 \S{output-man-characters} Configuring the characters used
1216 \dt \I{\cw{\\cfg\{man-charset\}}}\cw{\\cfg\{man-charset\}\{}\e{character set}\cw{\}}
1218 \dd Specifies what character set the output should be in, similarly to
1219 \cw{\\cfg\{text-charset\}} (see \k{output-text-characters}).
1221 \# FIXME: you're probably on your own in making sure that it's
1222 sensible to output man pages in that charset.
1224 \dt \I{\cw{\\cfg\{man-bullet\}}}\cw{\\cfg\{man-bullet\}\{}\e{text}\cw{\}}[\cw{\{}\e{text}\cw{\}}...]
1226 \dd Specifies the text to use as the \i{bullet} in bulletted lists.
1227 You can specify multiple fallback options. Works exactly like the
1228 \cw{\\cfg\{text-bullet\}} directive (see \k{output-text-characters}).
1230 \dt \I{\cw{\\cfg\{man-rule\}}}\cw{\\cfg\{man-rule\}\{}\e{text}\cw{\}}[\cw{\{}\e{text}...\cw{\}}]
1232 \dd This specifies the text which should be used for drawing
1233 \i{horizontal rules} (generated by \i\c{\\rule}; see
1234 \k{input-rule}) when the manual page is rendered into text.
1235 It should only be one character long, but otherwise
1236 it works like the \cw{\\cfg\{text-rule\}} directive
1237 (see \k{output-text-characters}).
1239 \dt \I{\cw{\\cfg\{man-quotes\}}}\cw{\\cfg\{man-quotes\}\{}\e{open-quote}\cw{\}\{}\e{close-quote}\cw{\}}[\cw{\{}\e{open-quote}\cw{\}\{}\e{close-quote}...\cw{\}}]
1241 \dd Specifies the quotation marks to use, overriding any
1242 \cw{\\cfg\{quotes\}} directive. You can specify multiple
1243 fallback options. Works exactly like the \cw{\\cfg\{text-quotes\}}
1244 directive (see \k{output-text-characters}).
1246 \S{output-man-defaults} Default settings
1248 The \i{default settings} for the \cw{man} page output format are:
1250 \c \cfg{man-filename}{output.1}
1252 \c \cfg{man-identity}{}
1254 \c \cfg{man-headnumbers}{false}
1255 \c \cfg{man-mindepth}{0}
1257 \c \cfg{man-charset}{ASCII}
1258 \c \cfg{man-bullet}{\u2022}{o}
1259 \c \cfg{man-rule}{\u2500}{-}
1260 \c \cfg{man-quotes}{\u2018}{\u2019}{"}{"}
1262 \H{output-info} GNU \c{info}
1264 This output format generates files which can be used with the \i{GNU
1267 There are typically multiple output files: a primary file whose name
1268 usually ends in \c{.info}, and one or more subsidiary files whose
1269 names have numbers on the end, so that they end in \c{.info-1},
1270 \c{.info-2} and so on. Alternatively, this output format can be
1271 configured to output a single large file containing the whole
1274 The \c{info} output format supports the following configuration
1277 \S{output-info-file} Controlling the output filenames
1279 \dt \I{\cw{\\cfg\{info-filename\}}}\cw{\\cfg\{info-filename\}\{}\e{filename}\cw{\}}
1281 \dd Sets the output file name in which to store the \c{info} file.
1282 This directive is implicitly generated if you provide a file name
1283 parameter after the command-line option \i\c{--info} (see
1284 \k{running-options}).
1288 The suffixes \c{-1}, \c{-2}, \c{-3} and so on will be appended to
1289 your output file name to produce any subsidiary files required.
1291 Note that \c{info} files refer to their own names internally, so
1292 these files cannot be \I{renaming \c{info} files}renamed after
1293 creation and remain useful.
1297 \dt \I{\cw{\\cfg\{info-max-file-size\}}}\cw{\\cfg\{info-max-file-size\}\{}\e{bytes}\cw{\}}
1299 \dd Sets the preferred \i{maximum file size} for each subsidiary
1300 file. As a special case, if you set this to zero, there will be no
1301 subsidiary files and the whole document will be placed in a single
1302 self-contained output file. (However, note that this file can still
1303 not be renamed usefully.)
1307 The preferred maximum file size is only a guideline. Halibut may be
1308 forced to exceed it if a single section of the document is larger
1309 than the maximum size (since individual \c{info} nodes may not be
1310 split between files).
1314 \S{output-info-dimensions} Indentation and line width
1316 \dt \I{\cw{\\cfg\{info-width\}}}\cw{\\cfg\{info-width\}\{}\e{width}\cw{\}}
1318 \dd Sets the \I{text width}width of the main part of the document,
1319 in characters. Works exactly like the \cw{\\cfg\{text-width\}}
1320 directive (see \k{output-text-dimensions}).
1322 \dt \I{\cw{\\cfg\{info-indent-code\}}}\cw{\\cfg\{info-indent-code\}\{}\e{indent}\cw{\}}
1324 \dd Specifies the extra indentation for \I{code paragraphs,
1325 indentation} code paragraphs. Works exactly like the
1326 \cw{\\cfg\{text-indent-code\}} directive (see
1327 \k{output-text-dimensions}).
1329 \dt \I{\cw{\\cfg\{info-index-width\}}}\cw{\\cfg\{info-index-width\}\{}\e{width}\cw{\}}
1331 \dd Specifies how much horizontal space to leave in the index node
1332 for the text of \i{index terms}, before displaying the sections the
1335 \dt \I{\cw{\\cfg\{info-list-indent\}}}\cw{\\cfg\{info-list-indent\}\{}\e{indent}\cw{\}}
1337 \dd Specifies the extra indentation before the bullet or number in a
1338 \I{bulletted list, indentation}\I{numbered list, indentation}list
1339 item. Works exactly like the \cw{\\cfg\{text-list-indent\}}
1340 directive (see \k{output-text-dimensions}).
1342 \dt \I{\cw{\\cfg\{info-listitem-indent\}}}\cw{\\cfg\{info-listitem-indent\}\{}\e{indent}\cw{\}}
1344 \dd Specifies the additional indentation before the body of a list
1345 item. Works exactly like the \cw{\\cfg\{text-listitem-indent\}}
1346 directive (see \k{output-text-dimensions}).
1348 \S{output-info-headings} Configuring heading display
1350 \dt \I{\cw{\\cfg\{info-section-suffix\}}}\cw{\\cfg\{info-section-suffix\}\{}\e{text}\cw{\}}
1352 \dd Specifies the suffix text to be appended to each section number
1353 before displaying the section title. For example, if you set this to
1354 \cq{:\_}, then a typical section title might look something like
1355 \q{Section 3.1: Something Like This}.
1357 \dt \I{\cw{\\cfg\{info-underline\}}}\cw{\\cfg\{info-underline\}\{}\e{text}\cw{\}}[\cw{\{}\e{text}\cw{\}}...]
1359 \dd Specifies the text to be used to underline section titles. Works
1360 very much like the \cw{\\cfg\{text-chapter-underline\}} directive
1361 (see \k{output-text-headings}). You can specify more than one
1362 option, and Halibut will choose the first one supported by the
1365 \S{output-info-characters} Controlling the characters used
1367 \dt \I{\cw{\\cfg\{info-charset\}}}\cw{\\cfg\{info-charset\}\{}\e{character set}\cw{\}}
1369 \dd Specifies what character set the output should be in, similarly to
1370 \cw{\\cfg\{text-charset\}} (see \k{output-text-characters}).
1372 \# FIXME: if you try sufficiently hard, you can probably find an
1373 output encoding that will break the info format by trampling on its
1374 special characters. So either don't do that, or tell us what we should
1377 \dt \I{\cw{\\cfg\{info-bullet\}}}\cw{\\cfg\{info-bullet\}\{}\e{text}\cw{\}}[\cw{\{}\e{text}\cw{\}}...]
1379 \dd Specifies the text to use as the \i{bullet} in bulletted lists.
1380 You can specify multiple fallback options. Works exactly like the
1381 \cw{\\cfg\{text-bullet\}} directive (see
1382 \k{output-text-characters}).
1384 \dt \I{\cw{\\cfg\{info-rule\}}}\cw{\\cfg\{info-rule\}\{}\e{text}\cw{\}}[\cw{\{}\e{text}\cw{\}}...]
1386 \dd Specifies the text used to draw \i{horizontal rules}. You can
1387 specify multiple fallback options. Works exactly like the
1388 \cw{\\cfg\{text-rule\}} directive (see \k{output-text-characters}).
1390 \dt \I{\cw{\\cfg\{info-quotes\}}}\cw{\\cfg\{info-quotes\}\{}\e{open-quote}\cw{\}\{}\e{close-quote}\cw{\}}[\cw{\{}\e{open-quote}\cw{\}\{}\e{close-quote}...\cw{\}}]
1392 \dd Specifies the quotation marks to use, overriding any
1393 \cw{\\cfg\{quotes\}} directive. You can specify multiple
1394 fallback options. Works exactly like the \cw{\\cfg\{text-quotes\}}
1395 directive (see \k{output-text-characters}).
1397 \dt \I{\cw{\\cfg\{info-emphasis\}}}\cw{\\cfg\{info-emphasis\}\{}\e{start-emph}\cw{\}\{}\e{end-emph}\cw{\}}[\cw{\{}\e{start-emph}\cw{\}\{}\e{end-emph}...\cw{\}}]
1399 \dd Specifies how to display emphasised text. You can specify
1400 multiple fallback options. Works exactly like the
1401 \cw{\\cfg\{text-emphasis\}} directive (see
1402 \k{output-text-characters}).
1404 \S{output-info-misc} Miscellaneous configuration options
1406 \dt \I{\cw{\\cfg\{info-list-suffix\}}}\cw{\\cfg\{info-list-suffix\}\{}\e{text}\cw{\}}
1408 \dd Specifies the text to append to the item numbers in a
1409 \i{numbered list}. Works exactly like the
1410 \cw{\\cfg\{text-list-suffix\}} directive (see
1411 \k{output-text-misc}).
1413 \dt \I{\cw{\\cfg\{info-dir-entry\}}}\cw{\\cfg\{info-dir-entry\}\{}\e{section}\cw{\}\{}\e{short
1414 name}\cw{\}\{}\e{long name}\cw{\}}[\cw{\{}\e{keyword}\cw{\}}]
1416 \dd Constructs an \i\cw{INFO-DIR-ENTRY} section and places it in the
1417 header of the Info file. This mechanism is used to automatically
1418 generate the \i{\c{dir} file} at the root of a Unix system's
1419 \c{info} collection.
1423 The parameters to this directive are:
1427 \dd Specifies the section of the \c{dir} file in which you want your
1428 document referenced. For example, \q{Development}, or \q{Games}, or
1433 \dd Specifies a short name for the directory entry, which will
1434 appear at the start of the menu line.
1438 \dd Specifies a long name for the directory entry, which will appear
1439 at the end of the menu line.
1443 \dd This parameter is optional. If it is present, then the directory
1444 entry will cause a jump to a particular subsection of your document,
1445 rather than starting at the top. The subsection will be the one
1446 referred to by the given keyword (see \k{input-sections} for details
1447 about assigning keywords to document sections).
1449 For example, in a document describing many game programs, the
1450 configuration directive
1452 \c \cfg{info-dir-entry}{Games}{Chess}{Electronic chess
1455 might produce text in the \c{dir} file looking something like this:
1458 \c * Chess: (mygames)Chapter 3. Electronic chess game
1460 if the output file were called \c{mygames.info} and the keyword
1461 \c{chess} had been used to define Chapter 3 of the document.
1465 \S{output-info-defaults} Default settings
1467 The \i{default settings} for the \c{info} output format are:
1469 \c \cfg{info-filename}{output.info}
1470 \c \cfg{info-max-file-size}{65536}
1472 \c \cfg{info-width}{70}
1473 \c \cfg{info-indent-code}{2}
1474 \c \cfg{info-index-width}{40}
1475 \c \cfg{info-list-indent}{1}
1476 \c \cfg{info-listitem-indent}{3}
1478 \c \cfg{info-section-suffix}{: }
1479 \c \cfg{info-underline}{\u203e}{-}
1481 \c \cfg{info-charset}{ASCII}
1482 \c \cfg{info-bullet}{\u2022}{-}
1483 \c \cfg{info-rule}{\u2500}{-}
1484 \c \cfg{info-quotes}{\u2018}{\u2019}{`}{'}
1485 \c \cfg{info-emphasis}{_}{_}
1487 \c \cfg{info-list-suffix}{.}
1489 and no \cw{\\cfg\{info-dir-entry\}} directives.
1491 \H{output-paper} Paper formats
1493 These output formats (currently PDF and PostScript) generate printable
1494 manuals. As such, they share a number of configuration directives.
1496 \S{output-pdf} \i{PDF}
1498 This output format generates a printable manual in PDF format. In
1499 addition, it uses some PDF interactive features to
1500 provide an outline of all the document's sections and clickable
1501 cross-references between sections.
1503 There is one configuration option specific to PDF:
1505 \dt \I{\cw{\\cfg\{pdf-filename\}}}\cw{\\cfg\{pdf-filename\}\{}\e{filename}\cw{\}}
1507 \dd Sets the \i{output file name} in which to store the PDF file.
1508 This directive is implicitly generated if you provide a file name
1509 parameter after the command-line option \i\c{--pdf} (see
1510 \k{running-options}).
1512 The \i{default settings} for the PDF output format are:
1514 \c \cfg{pdf-filename}{output.pdf}
1516 \S{output-ps} \i{PostScript}
1518 This output format generates a printable manual in PostScript format.
1519 This should look exactly identical to the PDF output (see
1520 \k{output-ps}), and uses \i\c{pdfmark} to arrange that if converted
1521 to PDF it will contain the same interactive features.
1523 There is one configuration option specific to PostScript:
1525 \dt \I{\cw{\\cfg\{ps-filename\}}}\cw{\\cfg\{ps-filename\}\{}\e{filename}\cw{\}}
1527 \dd Sets the \i{output file name} in which to store the PostScript
1528 file. This directive is implicitly generated if you provide a file
1529 name parameter after the command-line option \i\c{--ps} (see
1530 \k{running-options}).
1532 The \i{default settings} for the PostScript output format are:
1534 \c \cfg{ps-filename}{output.ps}
1536 \S{output-paper-dimensions} Configuring layout and \i{measurements}
1538 All measurements are in PostScript \i{points} (72 points to the inch).
1540 \S2{output-paper-pagesize} Page properties
1542 \dt \I{\cw{\\cfg\{paper-page-width\}}}\cw{\\cfg\{paper-page-width\}\{}\e{points}\cw{\}}
1544 \dt \I{\cw{\\cfg\{paper-page-height\}}}\cw{\\cfg\{paper-page-height\}\{}\e{points}\cw{\}}
1546 \dd Specify the absolute limits of the paper.
1548 \dt \I{\cw{\\cfg\{paper-left-margin\}}}\cw{\\cfg\{paper-left-margin\}\{}\e{points}\cw{\}}
1550 \dt \I{\cw{\\cfg\{paper-top-margin\}}}\cw{\\cfg\{paper-top-margin\}\{}\e{points}\cw{\}}
1552 \dt \I{\cw{\\cfg\{paper-right-margin\}}}\cw{\\cfg\{paper-right-margin\}\{}\e{points}\cw{\}}
1554 \dt \I{\cw{\\cfg\{paper-bottom-margin\}}}\cw{\\cfg\{paper-bottom-margin\}\{}\e{points}\cw{\}}
1556 \dd Specify the margins. Most text appears within these margins,
1561 \b Section numbers, which appear in the left margin.
1563 \b The footer (containing page numbers), which appears in the bottom
1568 \S2{output-paper-line} Vertical spacing
1570 \dt \I{\cw{\\cfg\{paper-base-leading\}}}\cw{\\cfg\{paper-base-leading\}\{}\e{points}\cw{\}}
1572 \dd Specifies the amount of space between lines of text within a
1573 paragraph. (So, if the font size is 12pt and there is 2pt of leading,
1574 there will be 14pt between successive baselines.)
1576 \dt \I{\cw{\\cfg\{paper-base-para-spacing\}}}\cw{\\cfg\{paper-base-para-spacing\}\{}\e{points}\cw{\}}
1578 \dd Specifies the amount of vertical space between paragraphs. (The
1579 vertical space between paragraphs does \e{not} include
1580 \c{paper-base-leading}.)
1582 \S2{output-paper-indentation} Indentation
1584 \dt \I{\cw{\\cfg\{paper-list-indent\}}}\cw{\\cfg\{paper-list-indent\}\{}\e{points}\cw{\}}
1586 \dd Specifies the indentation of the bullet or number in a
1587 \I{bulletted list, indentation}bulletted or \I{numbered list,
1588 indentation}numbered \I{list, indentation}list, similarly to
1589 \cw{\\cfg\{text-list-indent\}} (see \k{output-text-dimensions}).
1591 \dt \I{\cw{\\cfg\{paper-listitem-indent\}}}\cw{\\cfg\{paper-listitem-indent\}\{}\e{points}\cw{\}}
1593 \dd Specifies the \e{extra} indentation for the body of a list item,
1594 over and above the amount configured in \cw{\\cfg\{paper-list-indent\}}.
1596 \# FIXME: doesn't actually work, AFAICT.
1598 \dt \I{\cw{\\cfg\{paper-quote-indent\}}}\cw{\\cfg\{paper-quote-indent\}\{}\e{points}\cw{\}}
1600 \dd Specifies the amount of indentation for a level of quoting. Used
1601 for \cw{\\quote} (see \k{input-quote}) and code quotes with \cw{\\c}
1602 (see \k{input-code}).
1604 \S2{output-paper-headings} Headings
1606 \dt \I{\cw{\\cfg\{paper-chapter-top-space\}}}\cw{\\cfg\{paper-chapter-top-space\}\{}\e{points}\cw{\}}
1608 \dd Specifies the space between the top margin and the top of the
1609 chapter heading. (Each chapter begins on a new page.)
1611 \dt \I{\cw{\\cfg\{paper-chapter-underline-thickness\}}}\cw{\\cfg\{paper-chapter-underline-thickness\}\{}\e{points}\cw{\}}
1613 \dd Specifies the vertical thickness of the black rule under chapter
1616 \dt \I{\cw{\\cfg\{paper-chapter-underline-depth\}}}\cw{\\cfg\{paper-chapter-underline-depth\}\{}\e{points}\cw{\}}
1618 \dd Specifies the distance between the base of the chapter heading and
1619 the \e{base} of the underlying rule.
1621 \dt \I{\cw{\\cfg\{paper-sect-num-left-space\}}}\cw{\\cfg\{paper-sect-num-left-space\}\{}\e{points}\cw{\}}
1623 \dd Specifies the distance between the left margin and the \e{right}
1624 of section numbers (which are in the left margin).
1626 \S2{output-paper-index} Contents and index
1628 \dt \I{\cw{\\cfg\{paper-contents-index-step\}}}\cw{\\cfg\{paper-contents-index-step\}\{}\e{points}\cw{\}}
1630 \dt \I{\cw{\\cfg\{paper-contents-margin\}}}\cw{\\cfg\{paper-contents-margin\}\{}\e{points}\cw{\}}
1632 \# FIXME: I do not know what dees one does. (I couldn't get either of
1633 them to do anything obvious, although the source indicates they should
1636 \dt \I{\cw{\\cfg\{paper-leader-separation\}}}\cw{\\cfg\{paper-leader-separation\}\{}\e{points}\cw{\}}
1638 \dd Specifies the horizontal spacing between dots in \i\e{leaders}
1639 (the dotted lines that appear between section headings and page
1640 numbers in the table of contents).
1642 \dt \I{\cw{\\cfg\{paper-footer-distance\}}}\cw{\\cfg\{paper-footer-distance\}\{}\e{points}\cw{\}}
1644 \dd Specifies the distance between the bottom margin and the \e{base}
1645 of the footer (which contains page numbers).
1647 \dt \I{\cw{\\cfg\{paper-index-columns\}}}\cw{\\cfg\{paper-index-columns\}\{}\e{columns}\cw{\}}
1649 \dd Specifies the number of columns the index should be divided into.
1651 \# FIXME: with this set to 1, the right-alignment of some index entry
1652 page numbers in the Halibut manual is decidedly wonky.
1654 \dt \I{\cw{\\cfg\{paper-index-gutter\}}}\cw{\\cfg\{paper-index-gutter\}\{}\e{points}\cw{\}}
1656 \dd Specifies the amount of \I{gutter} horizontal space between index
1659 \dt \I{\cw{\\cfg\{paper-index-minsep\}}}\cw{\\cfg\{paper-index-minsep\}\{}\e{points}\cw{\}}
1661 \dd Specifies the minimum allowable horizontal space between an index
1662 entry and its page number. If the gap is smaller, the page number is
1663 moved to the next line.
1665 \S2{output-paper-fonts} \ii{Fonts}
1667 The directives in this section control which fonts Halibut uses for
1668 various kinds of text. Directives for setting the font normally take
1669 three font names, the first of which is used for normal text, the
1670 second for emphasised text, and the third for code. Any fonts which
1671 aren't specified are left unchanged. Fonts are named using their
1674 Halibut intrinsically knows about some fonts, and these fonts are also
1675 built into all PDF and most PostScript implementations. These are:
1679 \b \cw{Times-Italic}
1683 \b \cw{Times-BoldItalic}
1687 \b \cw{Helvetica-Oblique}
1689 \b \cw{Helvetica-Bold}
1691 \b \cw{Helvetica-BoldOblique}
1695 \b \cw{Courier-Oblique}
1697 \b \cw{Courier-Bold}
1699 \b \cw{Courier-BoldOblique}
1701 These fonts can be used without further formality. To use any other
1702 font, Halibut needs at least to know its measurements, which are
1703 provided in an \i{Adobe Font Metrics} (\I{AFM files}AFM) file.
1704 Halibut can also \I{embedding fonts}embed \i{Type 1 fonts} in its PDF
1705 and PostScript output if provided with font file in either hexadecimal (\I{PFA
1706 files}PFA) or IBM PC (\I{PFB files}PFB) format. To provide
1707 an AFM, PFA, or PFB file to Halibut, simply name it on Halibut's command
1708 line. If a PFA or PFB file is specified, the corresponding AFM file
1711 \ii{Font sizes} are specified in PostScript \i{points} (72 to the inch).
1713 \dt \I{\cw{\\cfg\{paper-title-fonts\}}}\cw{\\cfg\{paper-title-fonts\}\{}\e{normal-font}\cw{\}}[\cw{\{}\e{emph-font}\cw{\}}[\cw{\{}\e{code-font}\cw{\}}]]
1715 \dd Specifies the fonts to use for text in the document title.
1717 \dt \I{\cw{\\cfg\{paper-title-font-size\}}}\cw{\\cfg\{paper-title-font-size\}\{}\e{points}\cw{\}}
1719 \dd Specifies the \i{font size} of the document title.
1721 \dt \I{\cw{\\cfg\{paper-chapter-fonts\}}}\cw{\\cfg\{paper-chapter-fonts\}\{}\e{normal-font}\cw{\}}[\cw{\{}\e{emph-font}\cw{\}}[\cw{\{}\e{code-font}\cw{\}}]]
1723 \dd Specifies the fonts to use for text in chapter titles.
1725 \dt \I{\cw{\\cfg\{paper-chapter-font-size\}}}\cw{\\cfg\{paper-chapter-font-size\}\{}\e{points}\cw{\}}
1727 \dd Specifies the \i{font size} of chapter titles.
1729 \dt \I{\cw{\\cfg\{paper-section-fonts\}}}\cw{\\cfg\{paper-section-fonts\}\{}\e{level}\cw{\}\{}\e{normal-font}\cw{\}}[\cw{\{}\e{emph-font}\cw{\}}[\cw{\{}\e{code-font}\cw{\}}]]
1731 \dd Specifies the fonts to use for text in section headings at the \e{level}
1734 \dt \I{\cw{\\cfg\{paper-section-font-size\}}}\cw{\\cfg\{paper-section-font-size\}\{}\e{level}\cw{\}\{}\e{points}\cw{\}}
1736 \dd Specifies the \i{font size} of section headings at the \e{level}
1739 \dt \I{\cw{\\cfg\{paper-base-fonts\}}}\cw{\\cfg\{paper-base-fonts\}\{}\e{normal-font}\cw{\}}[\cw{\{}\e{emph-font}\cw{\}}[\cw{\{}\e{code-font}\cw{\}}]]
1741 \dd Specifies the fonts to use for text in the body text.
1743 \dt \I{\cw{\\cfg\{paper-base-font-size\}}}\cw{\\cfg\{paper-base-font-size\}\{}\e{points}\cw{\}}
1745 \dd Specifies the \i{font size} of body text.
1747 \dt \I{\cw{\\cfg\{paper-code-fonts\}}}\cw{\\cfg\{paper-code-fonts\}\{}\e{bold-font}\cw{\}}[\cw{\{}\e{italic-font}\cw{\}}[\cw{\{}\e{normal-font}\cw{\}}]]
1749 \dd Specifies the fonts to use for text in code paragraps. The
1750 \e{bold-font} is used for bold text, the \e{italic-font} for
1751 emphasised text, and the \e{normal-font} for normal code.
1753 \dt \I{\cw{\\cfg\{paper-code-font-size\}}}\cw{\\cfg\{paper-code-font-size\}\{}\e{points}\cw{\}}
1755 \dd Specifies the \i{font size} of text in code paragraphs.
1757 \dt \I{\cw{\\cfg\{paper-pagenum-font-size\}}}\cw{\\cfg\{paper-pagenum-font-size\}\{}\e{points}\cw{\}}
1759 \dd Specifies the font size to use for \i{page numbers}.
1761 \S2{output-paper-misc} Miscellaneous
1763 \dt \I{\cw{\\cfg\{paper-rule-thickness\}}}\cw{\\cfg\{paper-rule-thickness\}\{}\e{points}\cw{\}}
1765 \dd Specifies the vertical thickness of the rule produced by the
1766 \cw{\\rule} command (see \k{input-rule}). (Note that no extra space is
1767 reserved for thicker rules.)
1769 \S{output-paper-characters} Configuring the characters used
1771 \dt \I{\cw{\\cfg\{paper-bullet\}}}\cw{\\cfg\{paper-bullet\}\{}\e{text}\cw{\}}[\cw{\{}\e{text}\cw{\}}...]
1773 \dd Specifies the text to use as the \i{bullet} in bulletted lists.
1774 You can specify multiple fallback options. Works exactly like the
1775 \cw{\\cfg\{text-bullet\}} directive (see
1776 \k{output-text-characters}).
1778 \dt \I{\cw{\\cfg\{paper-quotes\}}}\cw{\\cfg\{paper-quotes\}\{}\e{open-quote}\cw{\}\{}\e{close-quote}\cw{\}}[\cw{\{}\e{open-quote}\cw{\}\{}\e{close-quote}...\cw{\}}]
1780 \dd Specifies the quotation marks to use, overriding any
1781 \cw{\\cfg\{quotes\}} directive. You can specify multiple
1782 fallback options. Works exactly like the \cw{\\cfg\{text-quotes\}}
1783 directive (see \k{output-text-characters}).
1785 \S{output-paper-defaults} Default settings for paper formats
1787 The default page size corresponds to 210\_\u00D7{x}\_297\_mm, i.e.,
1790 \c \cfg{paper-page-width}{595}
1791 \c \cfg{paper-page-height}{842}
1793 \c \cfg{paper-left-margin}{72}
1794 \c \cfg{paper-top-margin}{72}
1795 \c \cfg{paper-right-margin}{72}
1796 \c \cfg{paper-bottom-margin}{108}
1798 \c \cfg{paper-base-leading}{1}
1799 \c \cfg{paper-base-para-spacing}{10}
1801 \c \cfg{paper-list-indent}{6}
1802 \c \cfg{paper-listitem-indent}{18}
1803 \c \cfg{paper-quote-indent}{18}
1805 \c \cfg{paper-chapter-top-space}{72}
1806 \c \cfg{paper-chapter-underline-thickness}{3}
1807 \c \cfg{paper-chapter-underline-depth}{14}
1808 \c \cfg{paper-sect-num-left-space}{12}
1810 \c \cfg{paper-contents-index-step}{24}
1811 \c \cfg{paper-contents-margin}{84}
1812 \c \cfg{paper-leader-separation}{12}
1813 \c \cfg{paper-footer-distance}{32}
1814 \c \cfg{paper-index-columns}{2}
1815 \c \cfg{paper-index-gutter}{36}
1816 \c \cfg{paper-index-minsep}{18}
1818 \c \cfg{paper-base-fonts}{Times-Roman}{Times-Italic}{Courier}
1819 \c \cfg{paper-base-font-size}{12}
1820 \c \cfg{paper-code-fonts}{Courier-Bold}{Courier-Oblique}{Courier}
1821 \c \cfg{paper-code-font-size}{12}
1822 \c \cfg{paper-title-fonts}{Helvetica-Bold}
1823 \c {Helvetica-BoldOblique}{Courier-Bold}
1824 \c \cfg{paper-title-font-size}{24}
1825 \c \cfg{paper-chapter-fonts}{Helvetica-Bold}
1826 \c {Helvetica-BoldOblique}{Courier-Bold}
1827 \c \cfg{paper-chapter-font-size}{20}
1828 \c \cfg{paper-section-fonts}{0}{Helvetica-Bold}
1829 \c {Helvetica-BoldOblique}{Courier-Bold}
1830 \c \cfg{paper-section-font-size}{0}{16}
1831 \c \cfg{paper-section-fonts}{1}{Helvetica-Bold}
1832 \c {Helvetica-BoldOblique}{Courier-Bold}
1833 \c \cfg{paper-section-font-size}{1}{14}
1834 \c \cfg{paper-section-fonts}{2}{Helvetica-Bold}
1835 \c {Helvetica-BoldOblique}{Courier-Bold}
1836 \c \cfg{paper-section-font-size}{2}{13}
1837 \c ... and so on for all section levels below this ...
1838 \e iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
1840 \c \cfg{paper-pagenum-font-size}{12}
1842 \c \cfg{paper-rule-thickness}{1}
1844 \c \cfg{paper-bullet}{\u2022}{-}
1845 \c \cfg{paper-quotes}{\u2018}{\u2019}{'}{'}