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