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?
5 \cfg{xhtml-leaf-smallest-contents}{2}
6 \cfg{xhtml-leaf-contains-contents}{true}
7 \cfg{info-dir-entry}{Sillinesses}{test.but}{Halibut test document}
8 \cfg{info-dir-entry}{Florbles}{test.but}{Subsection of Halibut test
10 \cfg{man-headnumbers}{true}
12 This paragraph is not labelled \q{preamble}, but should still appear
15 \preamble This manual is a small joke effort, designed to use every
16 feature \#{ comment } that Halibut's input format supports. Creation
17 date \date{%Y.%m.%d} (default format is \date).
19 \c Here is a code paragraph in the preamble, just to stress that all
20 \c things are possible. Ooh!
22 \copyright Copyright 1999 Simon \#{second comment}Tatham. All rights
25 Here's another \i{preamble paragraph}, which goes after the copyright.
27 \define{metacoopt} [this is a nested,
28 multi-line macro, talking about \coopt
31 \define{coopt} co\u00F6{-o}pt
33 \define{eur} \u20AC{EUR }
37 \C{ch\\ap} First chapter title; for similar wrapping reasons this
38 chapter title will be ludicrously long. I wonder how much more
39 chapter title I can write before feeling silly.
41 This is a para\#{another{} comment}graph of text. It
42 has line\#{yet another one} breaks in between words, multiple
43 spaces (ignored), and \e{emphasised text} as well as \c{code
46 \cw{This} is weak code; \cq{this} is quoted code. And \k{head}
47 contains some other stuff. \K{subhead} does too.
49 To test the man page back end:
59 \\Sping\\Spong\\Spoing
61 \H{head} First section title (very long again, no prizes for
62 guessing the reason why this time, and here's yet more text to pad
63 it out to three lines of output)
65 \cfg{winhelp-topic}{M359HPEHGW}
67 Here's a code paragraph:
71 \c Two blank lines follow this one.
74 \c Two blank lines precede this one.
76 \c We can use \ { and } with impunity here.
77 \c We can use discretionary bold and italic in code paragraphs!
79 \c Isn't that ludicrous?
89 This bulletted list contains a list continuation. This is an
90 additional paragraph, or more than one, indented at the same level
91 as the list items, and able to contain nested sublists and other
92 features. For example, here's a code paragraph:
97 And here's a sublist. Numbered, just for variety.
114 \lcont{This is an even sillier one: a continuation of a list item in
115 a continuation of a list item in a continuation of a list item!}
127 This is a horizontal rule:
131 This is a numbered list:
137 \n Eek. \q{Aah} is point \k{keyword}.
139 This is a description list:
143 \dd A piscine creature, often to be found swimming aimlessly around
144 in the sea eating things and not contributing to the global economy.
148 Here's another of those funky list continuation things, just to keep
155 \dd A non-piscine creature, often to be found snuffling around on
156 land, not contributing to the global economy, and not even swimming
157 to make up for it. I don't know. These mammals. Pa-thetic.
159 \dt "SAUSAGE SALESMAN"
161 \dd An exemplary contributor to the global economy. Unless he's CMOT
164 This is a much more interesting description list, testing
165 consecutive \c{\\dt}s and consecutive \c{\\dd}s:
183 A-paragraph-full-of-hyphens-to-test-the-idea-that-word-wrapping-can-happen-somewhere-in-all-this-hyphenatory-nonsense.
185 A\-paragraph\-full\-of\-nonbreaking\-hyphens\-to\-test\-the\-idea\-that\-word\-wrapping\-misses\-them.
187 A\_paragraph\_full\_of\_nonbreaking\_spaces\_to\_test\_the\_idea\_that\_word\_wrapping\_misses\_them\_too.
189 Use of macros: let's talk about \coopt. And about \coopt some more.
190 And a nested macro: \metacoopt.
192 A slightly more difficult macro: \eur\.2500.
194 Test of input character set switching.
196 \n 8859 character in ASCII mode: expect nothing useful. [coöpt]
198 \cfg{input-charset}{ISO-8859-1}
200 \n 8859 character in 8859 mode: expect the right thing. [coöpt]
202 \cfg{input-charset}{UTF-8}
204 \n 8859 character in UTF-8 mode: expect the wrong thing. [coöpt]
206 \cfg{silliness}{coöpt}
208 \n UTF-8 sequence in UTF-8 mode: expect the right thing again. [coöpt]
210 \cfg{input-charset}{ASCII}
214 Oh, while I'm here: some special characters. The \\, \{ and \}
215 characters, to be precise. And their code equivalents, \c{\\},
218 \S{subhead} First subheading
220 So here's a \I{subheading}\I{subsection}subsection. Just
221 incidentally, \q{this} is in quotes. \ii{Those} quotes had better work
224 We'll try for some Unicode here: \i{Schr\u00F6{oe}dinger}.
226 An index tag containing non-alternatived Unicode: \i{\u00BFChe?}
228 An invisible index tag: \I{she seems to have an invisible tag}yeah.
230 \S2{sub-sub}{Florble} Smaller heading still
232 A tiny section. Awww. How cute. Actually, this one's a \e{florble},
233 and here's a reference to it: \k{sub-sub}.
235 \A{app} Needless appendix
237 \# \cfg{winhelp-topic}{Y5VQEXZQVJ} (uncomment this and it clashes)
239 Here's an \i{appendix}, for no terribly good reason at all. See
240 __\k{book}__ (please excuse those underscores, I'm testing
243 It also contains a \W{http://www.tartarus.org/}{hyperlink}.
245 Also I'm going to index \i\c{-output} to ensure that its two
246 components are displayed as a joined-up code fragment in the index.
248 Here are \I{testone}some \I{testtwo}subsections \I{testthree}with
249 silly chapter titles and interesting use of Unicode. The Unicode
250 oddities are in the titles rather than the body text because that
251 way I get to test their handling in the PDF document outline.
253 \H{app-one} The 1024 \u00D7{x} 768 screen resolution
257 \H{app-two} How about Spongletech\u2122{(TM)}?
261 \# I'm going to label one of these with a carefully chosen fragment
262 \# name "i1", because I know this will also be generated as an index
263 \# fragment name and this allows me to test the fragment name clash
266 \# To actually run this test you need to configure html-leaf-level
267 \# to 0 and html-template-fragment to %k.
269 \H{i1} Or just Erd\u0151{\u00F6{o}}s?
275 \B{book} Some text describing a book.
277 \B{nocite} Some text describing a book. This text should appear in
278 the document even though there is no \cw{\\k} citing it.
280 \BR{book} [SillyCitation]
285 \B{uncited} If this text appears, there's an actual error.
287 \# This is a comment.
289 \# Now for the index section.
291 \IM{she seems to have an invisible tag}{appendix} Invisible tags
294 \# The display forms of these three index terms differ only in case.
295 \# This is a fiddly special case in the Windows Help backend,
296 \# because Windows Help's index mechanism is case-insensitive...