Rename Buttress to Halibut. I _think_ I've caught everything in this pass.
[sgt/halibut] / inputs / test.but
1 \title Halibut: A Test Document With A Stupidly Long Title Just To
2 See If Wrapping Titles Works OK. In Fact This Title Will Span Three
3 Lines, Not Just Two. How's That For Ludicrous?
4
5 \cfg{xhtml-leaf-smallest-contents}{2}
6
7 \cfg{xhtml-leaf-contains-contents}{true}
8
9 \preamble This manual is a small joke effort, designed to use every
10 feature \#{ comment } that Halibut's input format supports. Creation
11 date \date{%Y.%m.%d} (default format is \date).
12
13 \copyright Copyright 1999 Simon \#{second comment}Tatham. All rights
14 reserved.
15
16 \define{metacoopt} [this is a nested,
17 multi-line macro, talking about \coopt
18 a bit]
19
20 \define{coopt} co\u00F6{-o}pt
21
22 \versionid $Id: test.but,v 1.18 2002/08/05 10:31:33 simon Exp $
23
24 \C{ch\\ap} First chapter title; for similar wrapping reasons this
25 chapter title will be ludicrously long. I wonder how much more
26 chapter title I can write before feeling silly.
27
28 This is a para\#{another{} comment}graph of text. It
29 has line\#{yet another one} breaks in between words, multiple
30 spaces (ignored), and \e{emphasised text} as well as \c{code
31 fragments}.
32
33 \cw{This} is weak code. And \k{head} contains some other stuff.
34 \K{subhead} does too.
35
36 \H{head} First section title (very long again, no prizes for
37 guessing the reason why this time, and here's yet more text to pad
38 it out to three lines of output)
39
40 \cfg{winhelp-topic}{M359HPEHGW}
41
42 Here's a code paragraph:
43
44 \c No leading spaces
45 \c One leading space
46 \c Two blank lines follow this one.
47 \c
48 \c
49 \c Two blank lines precede this one.
50 \c Two leading spaces
51 \c We can use \ { and } with impunity here.
52
53 This is a list:
54
55 \b Ooh.
56
57 \b Aah.
58
59 \b Eek.
60
61 This is a horizontal rule:
62
63 \rule
64
65 This is a numbered list:
66
67 \n Ooh.
68
69 \n{keyword} Aah.
70
71 \n Eek. \q{Aah} is point \k{keyword}.
72
73 A-paragraph-full-of-hyphens-to-test-the-idea-that-word-wrapping-can-happen-somewhere-in-all-this-hyphenatory-nonsense.
74
75 A\-paragraph\-full\-of\-nonbreaking\-hyphens\-to\-test\-the\-idea\-that\-word\-wrapping\-misses\-them.
76
77 A\_paragraph\_full\_of\_nonbreaking\_spaces\_to\_test\_the\_idea\_that\_word\_wrapping\_misses\_them\_too.
78
79 Use of macros: let's talk about \coopt. And about \coopt some more.
80 And a nested macro: \metacoopt.
81
82 Oh, while I'm here: some special characters. The \\, \{ and \}
83 characters, to be precise. And their code equivalents, \c{\\},
84 \i\c{\{}, \c{\}}.
85
86 \S{subhead} First subheading
87
88 So here's a \I{subheading}\I{subsection}subsection. Just
89 incidentally, \q{this} is in quotes. \ii{Those} quotes had better work
90 in all formats.
91
92 We'll try for some Unicode here: \i{Schr\u00F6{oe}dinger}.
93
94 An index tag containing non-alternatived Unicode: \i{\u00BFChe?}
95
96 An invisible index tag: \I{she seems to have an invisible tag}yeah.
97
98 \S2{sub-sub}{Florble} Smaller heading still
99
100 A tiny section. Awww. How cute. Actually, this one's a \e{florble},
101 and here's a reference to it: \k{sub-sub}.
102
103 \A{app} Needless appendix
104
105 \# \cfg{winhelp-topic}{Y5VQEXZQVJ} (uncomment this and it clashes)
106
107 Here's an \i{appendix}, for no terribly good reason at all. See
108 \k{book}.
109
110 It also contains a \W{http://www.tartarus.org/}{hyperlink}.
111
112 \U Bibliography
113
114 \B{book} Some text describing a book.
115
116 \B{nocite} Some text describing a book. This text should appear in
117 the document even though there is no \cw{\\k} citing it.
118
119 \BR{book} [SillyCitation]
120
121 \nocite{nocite}
122
123 \B{uncited} If this text appears, there's an actual error.
124
125 \# This is a comment.
126
127 \# Now for the index section.
128
129 \IM{she seems to have an invisible tag}{appendix} Invisible tags
130 and/or appendices